Skip to main content
Glama

Carfinity car marketplace

Get one car

get_car
Read-onlyIdempotent

Full details of one car: price against its market price, why it ranks where it does in plain sentences, mileage, color, drivetrain, photos count, the dealer and its phone, and the page to open. Use the id from search_cars.

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_id": "<car_id>"
    },
    "name": "get_car"
  }
}

Input Schema

NameRequiredDescriptionDefault
car_idYesThe 12-character id of the car, or its Carfinity URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real value by disclosing the returned content in detail (ranking explanation in plain sentences, market price comparison, dealer phone, page to open), which matters because no output schema exists. It omits auth requirements and error behavior for a bad id.

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 short sentences, purpose front-loaded, field enumeration packed densely rather than prose-heavy, and no redundant restatement of the title. The field list earns its place since there is no output 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?

For a single-parameter read tool with no output schema, it does the essential work: says what comes back and where the id comes from. Remaining gaps are edge-case handling (invalid id, missing car, auth) rather than core invocation guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema fully documents the single car_id parameter including the URL alternative. The description adds provenance guidance (take the id from search_cars) that the schema does not state, though it does not mention the URL form the schema allows.

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 resource and verb: full details of one car, then enumerates the payload fields (price vs market, ranking rationale, mileage, color, drivetrain, photos, dealer phone, page URL). It is clearly a single-record detail fetch, distinguishable from the plural-list sibling 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 Guidelines4/5

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

Explicitly says to use the id from search_cars, establishing the intended workflow (search first, then fetch detail). It stops short of stating exclusions or what to do when the id is unknown/invalid, and does not address when to prefer compare_cars over this.

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