Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses the return payload (top-N passages, character offsets, similarity scores) and the context-saving behavior, plus the ~200K char input ceiling via the schema. What it omits is operational behavior: error handling on oversized text, whether search is deterministic, and any latency or rate-limit expectations for a semantic model call.

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 purpose statement is well front-loaded, but the middle section is redundant: 'saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote' restates the payload already described in the first sentence. The description also terminates in a truncated fragment ('ground'), which reads as an editing failure rather than intentional brevity.

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 three-parameter, read-only retrieval tool with no output schema, the definition covers the essentials: what goes in, what comes back, and why an agent would choose it over inlining text. The dangling final clause about ask_pipeworx_grounded leaves the intended multi-tool workflow only half-explained, which is the main completeness gap.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning by characterizing the 'text' parameter as text 'you already pulled' with concrete instances (a SEC 10-K body, an article, a long tool result). That clarifies the intended granularity of the input in a way the schema's one-line property description does not. The 'limit' parameter is left entirely to 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 makes clear it operates on text the caller already has rather than fetching. That framing is enough to separate it from a fetch/gateway tool, and the 'what you get back' clause (top-N passages with offsets and similarity scores) removes any ambiguity about the output.

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 a clear triggering condition: 'Use when the record is too big to cram into the prompt.' It also gestures at the companion workflow ('fetch with the gateway, ground...'), implying fetch-then-search-then-ground. However, it never states when NOT to use it (e.g. small records that fit inline, or exact-string lookup) and the companion guidance is cut off mid-sentence, so alternatives are only partly specified.

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.