Skip to main content
Glama

Search dealer storefronts

search_dealers
Read-onlyIdempotent

Find dealers on the marketplace by name or town. Returns name, town, stock count and the public storefront url (no contact details).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_dealers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-30
queryNoname or town fragment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the read-only, idempotent, non-destructive, closed-world profile, so the description's main added value is the disclosure that results include name, town, stock count and storefront url but no contact details. That privacy/field-scope note is genuinely useful, though pagination limits and ordering of results are unaddressed.

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?

Two tight sentences with the purpose front-loaded and the returned fields enumerated second. No filler, though the parenthetical about contact details could have been folded more cleanly into a single clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Both parameters are documented in the schema and the description lists the result fields, which is enough to call the tool. With no output schema, however, it says nothing about result ordering, empty-result behavior, or whether limit truncates silently — relevant for a search surface.

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%, with 'limit' documented as 1-30 and 'query' as a name or town fragment. The description restates those two filters but adds no syntax, matching, or partial-match behavior beyond what the schema already says.

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 ('Find dealers on the marketplace') plus the filter dimensions ('by name or town') and even summarizes the return shape. It does not distinguish itself from the sibling get_dealer, which fetches a single dealer, leaving that routing decision to inference.

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

Usage Guidelines3/5

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

Usage is only implied by the word 'Find' and the mention of name/town fragments; there is no explicit statement of when to use this versus get_dealer or search_marketplace. An agent can guess this is the multi-result entry point, but the definition never says so.

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