Skip to main content
Glama

Carfinity car marketplace

Compare cars

compare_cars
Read-onlyIdempotent

Compare 2 to 4 cars side by side on price, market price, percent under market, score, rank, mileage and dealer, and say which is the best deal.

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": {
      "car_ids": "<car_ids>"
    },
    "name": "compare_cars"
  }
}

Input Schema

NameRequiredDescriptionDefault
car_idsYesCar ids from search_cars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 open-world behavior, so the safety profile is covered. Beyond that, the description discloses what the result contains — a comparison on named attributes plus a best-deal verdict — which annotations cannot express. It stops short of describing output shape or ordering, keeping it below the top mark.

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?

One front-loaded sentence with the scope constraint ('2 to 4 cars side by side') before the attribute list, and no filler. The attribute enumeration is long but each item conveys what the comparison returns, so it earns most of its length.

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?

For a read-only, single-parameter comparison tool with no output schema and full annotation coverage, the description supplies what is compared and that a best-deal judgment is produced. Only minor details — result ordering or handling of ties — are left unstated.

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 single parameter already documents 'Car ids from search_cars' with minItems/maxItems of 2-4. The description's '2 to 4 cars' restates the schema's bounds rather than adding new meaning, so this sits at the baseline for a fully documented single parameter.

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 ('Compare ... cars side by side') and enumerates the compared dimensions (price, market price, percent under market, score, rank, mileage, dealer), plus the outcome ('say which is the best deal'). That makes it clearly distinct from single-car siblings like get_car and from discovery tools like search_cars.

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 4 cars' bound tells the agent when the tool is applicable in size terms, and the schema points car ids back to search_cars. However, there is no explicit statement of when to prefer this over get_car calls or of any preconditions, so the usage guidance is implied rather than stated.

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