Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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 exist, so the description carries the full burden, and it does disclose meaningful behaviour: the tool saves context, returns only relevant passages rather than the whole document, and attaches a character offset to every passage so quotes can be verified verbatim. It omits cost, latency, failure behaviour on oversized input, and whether results are ranked or merely filtered, which keeps it below the top band.

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 core purpose and trigger are front-loaded in the first two sentences, which is good structure. However, the second sentence is a sprawling run-on and the description ends mid-sentence with 'fetch with the gateway, ground', a visibly truncated fragment that wastes space and reads as broken.

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?

With no output schema and no annotations, the description does the necessary work of describing the return shape (top-N passages plus offsets and similarity scores) and the context-saving rationale. It is nearly complete for a three-parameter read tool; only edge-case behaviour and the truncated final clause leave a gap.

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 coverage is 100%, so the schema already documents all three parameters including the query and the 1-20 limit with its default of 5. The description adds a little value by naming what 'text' can be (a SEC 10-K body, an article, a long tool result), but it does not explain ranking, offset units, or the ~200K char ceiling beyond what the schema states, so the baseline applies.

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 scope - 'Semantic search INSIDE a fetched record' - and immediately clarifies the input contract (pass text you already pulled plus a query) and the output (top-N passages with offsets and similarity scores). This distinguishes it from the sibling search/QA tools without needing to name them, since it operates on data the agent already holds.

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?

Gives an explicit trigger condition: 'Use when the record is too big to cram into the prompt.' It also gestures at the division of labour with ask_pipeworx_grounded ('fetch with the gateway, ground...'), clarifying this is the post-fetch step rather than a substitute. It stops short of stating when NOT to use it (e.g. small records, or when the agent hasn't fetched anything yet).

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.