Skip to main content
Glama

Carfinity car marketplace

Ask the dealer about a car

start_inquiry
Idempotent

Prepare a message to the dealer about one car on the shopper's behalf: availability, out-the-door price with fees, add-ons, history. Returns the exact message for the shopper to review. In this version the message is a preview and is not sent. Ask the shopper before calling this, and never invent their name or contact.

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>",
      "first_name": "<first_name>",
      "contact": "<contact>"
    },
    "name": "start_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoAnything else the shopper wants asked, in their words.
car_idYesCar id from search_cars.
contactYesEmail or mobile number the shopper wants answers sent to, as they gave it.
questionsNoWhat to ask. Default: availability and out-the-door price.
first_nameYesThe shopper's first name, as they gave it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the output is an unsent preview returned for shopper review, so despite readOnlyHint=false nothing is delivered to a third party. It also discloses the human-in-the-loop requirement to confirm with the shopper and the prohibition on fabricating name or contact, which the annotations cannot express.

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?

Three tightly packed sentences: purpose and fields first, then the return/preview semantics, then the safety constraint. No restatement of the name or title, and every clause carries new information.

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 still explains what comes back (the exact message for the shopper to review) and that it is not sent. For a five-parameter tool with annotations already covering safety and idempotency, nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description adds meaning by framing first_name and contact as values 'as they gave it' and forbidding invented values, and by enumerating the askable topics that correspond to the questions enum. It does not describe the note parameter's role or the default questions behavior, which the schema already covers.

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 ('Prepare a message to the dealer about one car') and enumerates the message contents (availability, out-the-door price with fees, add-ons, history). This clearly differentiates it from siblings like dealer_info, get_car, and search_cars, which retrieve data rather than compose a shopper-authored inquiry.

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?

Gives an explicit precondition: 'Ask the shopper before calling this, and never invent their name or contact,' plus the key context that the message is a preview and is not sent in this version. It lacks an explicit when-not-to-use or a named alternative (e.g., use dealer_info to just read dealer contact details), 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