Skip to main content
Glama

Preview search filters

spur_parse_search_query
Read-onlyIdempotent

Show how Spur interprets a plain-English property search (filters and events) without running it. Free: uses no data credits.

Use it to confirm intent before spending a credit, or to turn a vague request into explicit filters you can adjust. The returned arguments can be passed straight to spur_search_properties (keep the same location / status unless the user says otherwise). Exclusions ("no condos", "not foreclosures") are honoured by leaving those filters out.

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_search_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe user's search in their own words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), but the description adds genuinely new behavioral context: the call is free and consumes no data credits, and its output is designed to be piped into spur_search_properties. It does not spell out the returned structure (e.g. whether filters and events come back as separate keys), which keeps it short of a 5 for a tool with no output schema.

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

Conciseness5/5

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

Three sentences, front-loaded with the core purpose and the zero-cost trait before moving to usage and the handoff detail. Every sentence carries distinct information with no restatement of the title or name.

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 one-parameter, read-only preview tool with no output schema, the description covers purpose, cost, follow-up action, and input phrasing well enough to call it correctly. The only gap is the precise shape of the returned arguments, which matters slightly since there is no output schema to fall back on.

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% and the single query parameter is fully documented as "the user's search in their own words," so the schema does the heavy lifting. The description still adds meaning by framing what the parser extracts (filters and events) and how negative phrasing like "no condos" is handled, which guides how the agent should phrase input.

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 ("Show how Spur interprets a plain-English property search") and immediately distinguishes itself from the sibling that actually executes the search by saying "without running it." An agent can tell this preview tool apart from spur_search_properties without opening either schema.

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 when-to-use conditions ("confirm intent before spending a credit," "turn a vague request into explicit filters you can adjust") and names the alternative it feeds into (spur_search_properties) with a caveat about keeping the same location/status. It even resolves a common ambiguity by explaining that exclusions are expressed by omission, not by a filter flag.

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