Skip to main content
Glama

Carfinity car marketplace

Summarize a market

market_summary
Read-onlyIdempotent

How many of a model (or kind of car) are for sale in a market, the median advertised price and mileage, the price range, and the share priced under market. Use it for questions like 'what does a used Camry cost in Dallas' or 'is now a good time'.

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": "market_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA model or kind of car, with new or used, for example 'used Toyota Camry', 'new Ford F-150', 'used SUV under $30k'.
marketNoMarket slug from list_markets. Optional if the query names the city.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is fully covered. The description adds meaningful behavioral detail by specifying that prices are 'advertised' rather than transaction prices and that results are aggregated statistics (median, range, share under market) rather than individual listings. It does not mention sample-size thresholds, time windows, or what happens when a market has no listings, which limits it to a 3.

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 sentences, zero waste. The returned metrics are listed first so an agent knows the payload shape immediately, and the examples follow as a compact usage cue.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so by enumerating the five aggregate metrics. Some definitional gaps remain (what 'market price' baseline drives 'share priced under market', whether results are time-bounded), but for a two-parameter read-only tool it is largely complete.

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 both 'query' and 'market' fully documented including the pointer to list_markets and the note that market is optional when the query names a city. The description restates the same concepts ('a model (or kind of car)', 'in a market') without adding syntax or format detail beyond the schema, so 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 (a model or kind of car in a market) and enumerates exactly what the summary computes: listing count, median advertised price and mileage, price range, and share priced under market. This clearly reads as an aggregate/market-statistics tool rather than a listing search, though it never names a sibling such as search_cars or compare_cars to sharpen the distinction.

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?

Two example questions ('what does a used Camry cost in Dallas', 'is now a good time') give concrete usage context that implies price-checking and timing decisions. However, there is no explicit when-not guidance and no mention of alternatives, so an agent must infer that listing-level lookups belong to search_cars or get_car.

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