Skip to main content
Glama

Model market snapshot

market_snapshot
Read-onlyIdempotent

Figures for one model as Census EV publishes them on its model page and its market page: how many are for sale and as of when; cars for sale and median asking price by model year; the mileage-adjusted asking price of a used one at 40,000 miles with its 30- and 60-day change; and the share of used ones no longer listed 30 days after they appeared, with the window it was measured over. A figure is null or absent where the site prints none, because too few cars stand behind it or it could not be read.

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": {
      "make": "<make>",
      "model": "<model>"
    },
    "name": "market_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesMake, e.g. "Hyundai". Case, spacing and common short forms ("Chevy", "VW") are accepted.
modelYesModel, e.g. "Ioniq 5". Punctuation and spacing are ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds genuinely useful behavior beyond them: figures reflect what the source site publishes, are timestamped ('as of when'), carry explicit measurement windows for the 30/60-day price change and the 30-day delisting share, and are null or absent when too few cars back them or the value could not be read. That null semantics and provenance detail is exactly the kind of context annotations cannot convey.

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?

The purpose is front-loaded and the single long sentence is dense with the returned metrics, with the null caveat closing it. It reads more like a list of figures than a crisp statement of purpose, but no clause is filler and nothing is repeated from 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?

With no output schema, the description carries the burden of describing return values and does so by enumerating each figure and its measurement window, plus the null rule. The main thing left unstated is geographic or dataset scope (implied US by the source) and the response shape, but an agent still has everything needed to call and interpret it.

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 parameter descriptions already cover case, spacing, short forms and punctuation tolerance. The description contributes nothing additional about make/model beyond confirming the tool is scoped to one model, so the baseline 3 applies.

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?

The description names a specific resource ('Figures for one model as Census EV publishes them') and scopes it precisely to a single make/model, enumerating exactly what figures are returned: for-sale counts, per-year median asking prices, a mileage-adjusted price at 40,000 miles, and a 30-day delisting share. That is unmistakably distinct from the sibling tools that return individual listings (get_listing, search_listings) or enumerate models (list_models).

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: an agent can infer this is the tool for aggregate market stats on one model rather than raw listings. There is no explicit statement of when to prefer it over search_listings or get_listing, and no prerequisites or exclusions are given, so the routing decision is left to inference.

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