Skip to main content
Glama

Dev Feeds

by io.github.pipeworx-io

Search Within a Source

search_within
Read-onlyIdempotent

Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt — search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe document text to search inside (max ~200K chars).
limitNoMax passages to return (1-20, default 5).
queryYesNatural-language query — what passages do you want? E.g. "supply-chain risk", "fiscal year 2024 revenue", "drug interactions with warfarin".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. Description adds: embedding model (BGE-base-en), similarity metric (cosine), chunking (500-char overlapping windows), character limit (200K with truncation/flagging), and offset for passages. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences packed with purpose, use case, benefits, workflow pairing, and technical details. No wasted words; front-loaded with core message.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, description explains return format (passages with offsets and scores). Covers all relevant details: input constraints, tech specs, and integration hints. Fully equips agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema provides 100% coverage with descriptions. Description adds nuanced context: 'text' is 'already pulled' content, 'query' has example phrases, 'limit' has default and range. Supplies meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title and first sentence immediately specify 'semantic search INSIDE a fetched record.' It clearly differentiates from sibling tools by describing its specific use case (large documents) and relationship with ask_pipeworx_grounded.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use when the record is too big to cram into the prompt' and pairs with ask_pipeworx_grounded for workflow guidance. Lacks explicit when-not-to-use but provides strong contextual direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Dev Feeds toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have distinct purposes, but there is some overlap between ask_pipeworx, ask_pipeworx_grounded, deep_research, and similar data query tools. However, detailed descriptions help agents differentiate.

Naming Consistency4/5

Names consistently use snake_case and a mix of verb_noun and noun_verb patterns. No camelCase is present, but some tools like 'generate_llms_txt' have embedded acronyms, which slightly reduces consistency.

Tool Count3/5

33 tools is high, but the server covers a wide range of functionalities (data lookups, prediction markets, RSS feeds, memory). Some tools could be combined, but the count is within reasonable limits for a comprehensive tool server.

Completeness4/5

The tool set covers major areas like entity lookups, prediction market analysis, data retrieval, and memory management. Minor gaps exist (e.g., no RSS feed deletion tool), but overall it is quite comprehensive.

Resources