Skip to main content
Glama

Compare cars

compare_listings
Read-only

Puts two or three of the cars that see_cars_near_buyer returned side by side. It takes their handles. It answers cars (each with a short title, and condition, new or used, when the listing says) and rows: year, trim, exterior color, mileage and the listed price, one value per car. same is true when every car has the same value, false when they differ, and null when a car has no value. A value a car does not have is null. The listed price is before taxes and dealer fees. The answer names no dealership.

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

Input Schema

NameRequiredDescriptionDefault
handlesYesTwo or three handles from see_cars_near_buyer. A handle works for 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world. The description adds behavior the agent cannot infer elsewhere: the exact answer shape (`cars`, `rows`, `same`), the tri-state semantics of `same`, how missing values are represented, and that listed prices exclude taxes and dealer fees. The 24-hour handle lifetime it mentions is already in the schema, which slightly dilutes the added value.

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?

Short sentences, scope and input requirement front-loaded, and every statement carries information. Minor redundancy between '`same` is ... null when a car has no value' and 'A value a car does not have is null', and the choppy one-clause cadence costs a little flow.

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 no output schema, the description fully carries the return contract (per-car titles/condition, row fields, same-flag semantics, null handling) plus a pricing caveat, which is everything an agent needs to call this one-parameter read tool correctly.

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 sole parameter already documents the two-to-three handle constraint and the 24-hour lifetime. The description only restates 'It takes their `handles`', adding no syntax or format detail beyond the schema, so the baseline of 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?

States a specific verb and resource ('Puts two or three of the cars ... side by side') and anchors the tool to its sibling by requiring handles that `see_cars_near_buyer` returned. An agent can tell it apart from catalog-browsing siblings without opening the schema.

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

Usage Guidelines4/5

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

The provenance requirement ('cars that `see_cars_near_buyer` returned') tells the agent when this tool applies, namely after a search. It does not name an alternative or a when-not condition, so it stops short of full routing guidance.

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