Skip to main content
Glama

NS Pros MCP Gateway

nist-standards__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": "nist-standards__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?

With no annotations supplied, the description carries the behavioral burden and does reasonably well: it discloses that only top-N matching passages return, that each carries a character offset and similarity score, and that offsets exist so a verbatim quote can be verified. It omits any statement about cost/latency or whether the input text is stored, which keeps it short of a 5 for an unannotated tool.

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 value proposition is front-loaded and the middle is efficient, but the final sentence is a broken fragment ('fetch with the gateway, ground') that adds no usable information, and the 'search_within saves context' clause reads as a comma splice. Trimming the dangling pairing note would improve it noticeably.

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?

Because there is no output schema, the description must explain the return value, and it does — top-N passages with character offsets and similarity scores. Combined with a fully documented three-parameter schema, an agent has enough to call this correctly; only the truncated companion-tool sentence leaves a loose end.

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 baseline is 3 — the schema already defines text, query, and limit with their own descriptions and ranges. The description adds only marginal semantics, clarifying that 'text' should be content previously pulled from somewhere else, but does not elaborate on limit behavior or passage granularity 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?

The opening sentence gives a specific verb and resource — 'Semantic search INSIDE a fetched record' — and explicitly scopes it to text the caller already retrieved. That cleanly separates it from the sibling fetch/search tools, and the following sentence describes the exact input/output exchange (text + query -> top-N passages with offsets and scores).

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?

It states a concrete trigger: 'Use when the record is too big to cram into the prompt,' and points at a companion tool ('Pairs with ask_pipeworx_grounded: fetch with the gateway, ground...'). There is no explicit when-not guidance, and the pairing sentence trails off mid-thought, so the alternative-selection logic is only partly spelled out.

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.