Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does a solid job: it describes the return contents precisely (top-N passages with character offsets and similarity scores), states the context-saving behaviour, and explains why offsets matter (verbatim quote verification). It omits cost/latency, whether anything is persisted, and how empty or over-limit results behave.

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 second sentence is a run-on that slips into third-person self-reference ("search_within saves context") and the closing sentence trails off in an unfinished fragment ("fetch with the gateway, ground"). Content is mostly earning its place, but the structure needs tightening and the truncated tail should be repaired or cut.

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, non-mutating search tool with no output schema and no annotations, the description covers purpose, trigger condition, return shape, and verification value of offsets. Remaining gaps (failure/empty-result behaviour, hard truncation beyond the size cap) are modest given the tool's simplicity.

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%, so the schema already documents text (max ~200K chars), query, and limit (1-20, default 5). The description reinforces 'text you already pulled' and 'natural-language query' and implies top-N via limit, but adds no syntax, sizing, or formatting guidance the schema lacks. Baseline 3 applies.

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

Purpose4/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 makes the input domain concrete ("text you already pulled ... a SEC 10-K body, an article, a long tool result"). It is clearly distinct from prompt-stuffing and names a related sibling (ask_pipeworx_grounded), though it does not sharply bound itself against other search-flavoured siblings.

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", plus a stated benefit (saves context, returns only relevant passages). It also positions a companion tool (ask_pipeworx_grounded) and a workflow (fetch with the gateway, then ground). No explicit when-not or negative case, and the final clause is truncated mid-thought.

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.