Skip to main content
Glama

Compare listings

compare_listings
Read-onlyIdempotent

Two to five listings by VIN, side by side: for each, its full record with its asking-price history, battery_warranty and asking_vs_similar where they exist. VINs with no live listing are returned in not_found, and any that could not be read in time in unavailable. Results are as of the as_of timestamp.

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": {
      "vins": "<vins>"
    },
    "name": "compare_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinsYes2 to 5 VINs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: missing VINs land in not_found, timed-out reads land in unavailable, and all results are as of an as_of timestamp. That partial-failure and freshness disclosure is exactly the kind of context annotations cannot carry; only auth/rate-limit details are absent.

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, no filler, and the primary payload description is front-loaded before the edge-case buckets. The dense packing of return fields is information, not padding.

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

Completeness5/5

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

With one parameter, no output schema, and full annotation coverage, the description supplies everything an agent needs: input scope, the shape of each returned record, the two failure buckets, and result freshness. Nothing material is left for the caller to guess.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines vins, the 17-character format, and the 2-5 bounds. The description restates the 2-to-5 range but adds no format or validation detail beyond the schema, which is the expected baseline here.

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 a specific verb and resource ('listings by VIN, side by side') plus scope (two to five), and enumerates what each entry contains (full record, asking-price history, battery_warranty, asking_vs_similar). An agent can immediately tell this is a batch comparison rather than a single-record fetch.

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?

The 2-to-5 VIN bound and 'side by side' framing imply the batch-comparison use case, and the not_found/unavailable handling implies it tolerates partial input. However, it never states when to prefer this over get_listing for one VIN or search_listings when VINs are unknown, so routing 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