Skip to main content
Glama

Preview a Data Search

spur_parse_data_search
Read-onlyIdempotent

Turn a plain-English request into a Data Search (filters, recipe, and provider choice) without searching or charging. Recipe requests can run directly with spur_run_data_job; other searches require confirmation before spur_data_search. Providers are only fixed when the user named one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "spur_parse_data_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, so the description's value is in adding 'without searching or charging' (no credits consumed, no execution) and the inference rule 'Providers are only fixed when the user named one'. It doesn't address ambiguous or failed parses, so it stops short of full behavioral coverage.

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

Conciseness4/5

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

Three sentences, front-loaded with the core action, then routing, then a caveat. Dense and mostly waste-free, though the compressed phrasing around 'recipe' assumes domain familiarity.

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, the description compensates by naming the shape of the result (filters, recipe, provider choice). Combined with the no-charge, no-search guarantee and the next-step routing, an agent has enough to call it correctly; only edge-case behavior on unparseable input is absent.

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?

Only one parameter and schema description coverage is 0% (just length bounds), so the description has to carry meaning. 'Plain-English request' usefully tells the agent the query is natural language rather than structured syntax, but nothing is said about length limits, phrasing guidance, or examples.

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: 'Turn a plain-English request into a Data Search (filters, recipe, and provider choice)'. It also draws the line against both relevant siblings: no actual search (vs spur_data_search) and no charge. An agent can place it precisely without opening sibling schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: recipe requests can go straight to spur_run_data_job, other searches need confirmation before spur_data_search. The condition that selects each alternative is named, not merely implied.

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.

Resources