Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__search_within

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

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "Apple Inc. reported fiscal 2023 revenue of $383.285 billion, driven by strong iPhone and Services growth. Net income was $96.995 billion. The company faced supply-chain risk in China during the quarter.",
      "query": "supply-chain risk"
    },
    "name": "npi-registry__search_within"
  }
}

Input 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.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does substantial work: it discloses the return shape (top-N passages with character offsets and similarity scores), the context-economy rationale, and the verification affordance of offsets for verbatim quotes. It does not cover failure modes such as oversized input or empty matches, nor cost/latency behavior.

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

Conciseness3/5

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

The opening is well front-loaded, but the middle sentence is a comma splice run-on ('Use when the record is too big..., search_within saves context, returns only...') and the final sentence is truncated mid-clause ('fetch with the gateway, ground'), leaving an incomplete thought in the definition. The core content earns its place; the execution is sloppy.

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

Completeness4/5

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

For a 3-parameter read tool with no output schema, the description supplies the essential coverage: what goes in, what comes back, and why it matters for context budget. The unfinished closing sentence about pairing with ask_pipeworx_grounded leaves the composition guidance incomplete.

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

Parameters3/5

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

Schema description coverage is 100%, including examples for text, query, and the limit range, so the baseline is 3. The description adds framing that 'text' is content already retrieved (10-K body, article, long tool result) and that the query is natural-language, but gives no new syntax, sizing, or formatting guidance beyond the 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?

States a specific verb and resource ('Semantic search INSIDE a fetched record') and immediately scopes it to text the agent already pulled, which cleanly separates it from the retrieval-style siblings like company_register_search or npi_registry_search. An agent can tell from the first sentence that this tool does not fetch anything itself.

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?

'Use when the record is too big to cram into the prompt' gives an explicit trigger condition with the rationale (saves context). It also names a companion tool, ask_pipeworx_grounded, for the fetch-then-ground workflow. There is no explicit when-not or statement of what to do instead for small records, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.