Skip to main content
Glama

Carfinity car marketplace

Look up a dealer

dealer_info
Read-onlyIdempotent

A dealer's name, address, phone and website, how many new and used cars it has listed, and its best-ranked cars.

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": {
      "dealer": "<dealer>"
    },
    "name": "dealer_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
dealerYesDealer name or website domain.
marketNoMarket slug, to narrow a common name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds value by outlining the returned payload in the absence of an output schema, but says nothing about what happens when a dealer name is ambiguous, whether results can be empty, or what 'best-ranked' means.

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?

A single compact sentence with no filler, and the itemization of returned fields is easy to scan. It is front-loaded on the domain object, though the list-form phrasing makes it slightly less scannable than a verb-led sentence would be.

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?

Given no output schema, listing the returned fields is the right move and largely covers the payload. However, for an open-world lookup tool with no annotation on result cardinality, the description omits what happens on no-match or multiple-match input and leaves 'best-ranked' undefined.

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%, so both parameters (dealer name/domain and market slug) are already documented in the schema. The description does not elaborate on input format, matching behavior, or how market narrows a common name, so the 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?

The description names the resource and enumerates the specific data returned (contact details, new/used inventory counts, top-ranked cars), which clearly distinguishes it from car- or market-oriented siblings. It reads as a noun phrase rather than a verb, relying on the title for the 'look up' action, but the content is concrete enough for an agent to identify it.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no reference to alternatives such as get_car or market_summary. The only implied usage comes from the title 'Look up a dealer', leaving the agent to infer the triggering conditions itself.

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