SYMONE motorcycle transport

Send a quote request (confirmed by the customer by e-mail)

request_quote

Destructive

Send a quote request (demande de devis) to SYMONE for the customer, for any route and date, including routes not listed by search_routes. Nothing is recorded until the customer confirms: SYMONE e-mails them a link (valid 48 h) to check the request, accept the terms and confirm. The quote then arrives by e-mail (minutes for common routes, otherwise within one business day). No payment. Ask the customer before sending their name, e-mail and phone. Returns the request id, its status and the cities as SYMONE understood them; fix the listed fields if the request is refused.

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": {
      "departure_city": "<departure_city>",
      "arrival_city": "<arrival_city>",
      "departure_date": "<departure_date>",
      "customer": "<customer>"
    },
    "name": "request_quote"
  }
}

Input Schema

Name	Required	Description	Default
`return`	No	Required when trip_type is round_trip. Cities default to the outbound trip reversed; motorcycles and riders default to the outbound ones.
`riders`	No	People travelling with the motorcycles (motorcycle + rider service). 0 = motorcycles only.
`comment`	No	Anything useful for the SYMONE team.
`customer`	Yes	The customer the quote is for. The confirmation e-mail goes to this address.
`trip_type`	No		one_way
`motorcycles`	No	One entry per motorcycle (scooters, trikes and side-cars included).
`arrival_city`	Yes	Where they are delivered (same formats).
`discount_code`	No
`paris_details`	No	Required when Paris is the departure or arrival: arrondissement, nearby town or flexibility ('15e', 'Boulogne-Billancourt', 'flexible').
`departure_city`	Yes	Where the motorcycles are picked up, e.g. 'Paris 15e', 'Marseille', '93200 Saint-Denis' or 'Barcelona, Spain'.
`departure_date`	Yes	Wanted date YYYY-MM-DD, or a period in words ('mid-December', 'between 10 and 15 March').
`idempotency_key`	No	Optional unique key (e.g. a UUID): a retried call with the same key never sends a second e-mail.
`cancellation_insurance`	No	Quote the optional cancellation insurance.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / customer / properties / civility / description

Previous value: -"Optional: M (Monsieur), F (Madame) or X (none)."New value: +"Optional, only if the customer gave it: M (Monsieur), F (Madame) or X (none). Never guess it from the first name."

AddedNov 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With destructiveHint=true and openWorldHint=true already declared, the description still adds substantial context: nothing is recorded until the customer confirms, an e-mail link valid 48 h is sent, quote timing (minutes vs one business day), no payment, and what to do if the request is refused. This explains the real-world side effects in a way the annotations cannot.

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?

Front-loaded with the purpose, then behavior, then the consent prerequisite, then the return value — a sensible order. The single dense paragraph is slightly packed, but essentially every sentence carries 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?

For a 13-parameter, nested-object, mutation-style tool with no output schema, the description covers purpose, side effects, timing, consent requirements, and return contents. Nothing an agent needs in order to call it safely 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 already 85%, so the baseline is 3; the description adds meaning by explaining that the returned cities are 'as SYMONE understood them' and that fields must be corrected on refusal, and by flagging which customer data is being transmitted. It does not discuss trip_type, discount_code or cancellation_insurance, which the schema covers anyway.

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 ('Send a quote request to SYMONE for the customer') plus the scope that distinguishes it from siblings: 'for any route and date, including routes not listed by search_routes'. An agent can immediately tell this apart from search_routes and get_quote_request.

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 a clear selection rule against search_routes (use this even when the route is not listed) and a prerequisite ('Ask the customer before sending their name, e-mail and phone'). It does not explicitly point to get_quote_request for follow-up status checks, which is the one obvious gap.

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

All SYMONE motorcycle transport 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?