Car Handshake

Send a vehicle inquiry

submit_vehicle_inquiry

DestructiveIdempotent

After explicit consent and confirmation, send this listing's dealer a question.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	No	Email (or phone required).
`phone`	No	E.164 phone (or email required).
`dry_run`	No	Validate with no dealer contact.
`message`	Yes	Dealer note.
`last_name`	Yes	Last name.
`first_name`	Yes	First name.
`listing_id`	Yes	Exact listing_id from prior results.
`consent_text`	Yes	Accepted consent words; never fabricate consent.
`idempotency_key`	Yes	Unique retry key.
`allowed_channels`	Yes	Consent channels.
`preferred_contact`	No
`consent_granted_at`	Yes	Consent timestamp (RFC 3339).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`lead_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedAug 18, 2026

changedInput schema / properties / allowed_channels / description

Previous value: -"Accepted channels."New value: +"Consent channels."

changedInput schema / properties / consent_granted_at / description

Previous value: -"Consent time, RFC 3339 with timezone."New value: +"Consent timestamp (RFC 3339)."

changedInput schema / properties / consent_text / description

Previous value: -"Exact accepted words; never fabricate consent."New value: +"Accepted consent words; never fabricate consent."

changedInput schema / properties / dry_run / description

Previous value: -"Validate only; no dealer contact."New value: +"Validate with no dealer contact."

changedInput schema / properties / email / description

Previous value: -"Email; email or phone required."New value: +"Email (or phone required)."

changedInput schema / properties / listing_id / description

Previous value: -"Exact listing_id from prior read."New value: +"Exact listing_id from prior results."

changedInput schema / properties / message / description

Previous value: -"Optional dealer note."New value: +"Dealer note."

changedInput schema / properties / phone / description

Previous value: -"E.164 phone; email or phone required."New value: +"E.164 phone (or email required)."

First observedAug 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover readOnly/destructive/idempotent hints, so the bar is lower. The description adds the crucial consent requirement and states that the tool sends an external message to the dealer, which is a side effect. This provides useful context beyond the annotations.

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?

The description is a single sentence that is front-loaded with the consent condition and states the action and target. Every word earns its place, with no redundancy or padding.

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?

The tool has many parameters, but the schema is rich with descriptions. The description covers the essential purpose and the critical consent requirement. An output schema exists, so the description need not explain return values. It is adequate but not exhaustive for such a multi-parameter external side-effect tool.

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 description coverage is high (92%), so the baseline is 3. The description adds no specific parameter semantics; the consent-related parameters are already well described in the schema. The consent phrase in the description reinforces but does not exceed schema content.

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?

The description uses a specific verb ('send') and identifies the resource ('this listing's dealer a question'), clearly distinguishing it from sibling tools like schedule_test_drive or search. It also includes the important prerequisite of consent, adding scope.

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 description implies usage after explicit consent and confirmation, giving a clear condition for when to invoke. It does not explicitly mention alternatives or exclusions, but the tool's function is distinct among siblings, making the context clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Car Handshake tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?