Skip to main content
Glama

67Leads

Parse a search sentence

parse_query
Read-onlyIdempotent

What a plain-English lead search means (niche, city, state, filters) without running it. Free.

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": {
      "q": "<q>"
    },
    "name": "parse_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesPlain-English search, e.g. 'roofers in Dallas TX with no website'. Explicit fields below override what the sentence says.

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?

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, so the safety bar is low. The description still adds real value by disclosing that the query is not executed and that the call is free, which matters for cost-aware planning. It does not describe how ambiguous or unparseable input is reported, leaving the output contract under-specified.

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?

Two short clauses with the most important qualifier (not executed) and the cost signal front-loaded. Nothing is redundant with the title or the schema.

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 parsing tool with no output schema, the description gives enough to call it correctly: input shape, output concept, cost, and non-execution. The remaining gap is the shape of the returned parse and any error or ambiguity behavior.

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% and the single parameter already carries an example plus the precedence rule that explicit fields override the sentence. The description adds only the field categories the sentence is decomposed into, which is marginal beyond what the schema states.

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 precisely what the tool produces: an interpretation of a plain-English lead search broken into niche, city, state, and filters. The phrase 'without running it' immediately separates it from search_leads, so an agent can pick the right tool without opening the schema.

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?

'Without running it. Free.' gives a clear usage context: use this to preview or validate an interpretation before spending a search. It does not explicitly name search_leads or count_leads as the alternative, nor state what to do when the parse looks wrong, so it falls short of full when/when-not guidance.

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