Calculates a dry-run ride fare quote from pickup and destination coordinates and service type, letting users preview Snapp pricing before confirming a booking.
Flexi quote (dry-run)
| Name | Required | Description | Default |
|---|---|---|---|
| token | No | ||
| to-lat | No | ||
| to-lng | No | ||
| confirm | No | ||
| service | No | ||
| from-lat | No | ||
| from-lng | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. '(dry-run)' does usefully imply the operation is non-mutating, but nothing is said about authentication (the token parameter), rate limits, permissions, or what happens on confirm=true versus confirm=false.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is short, but that brevity reflects under-specification rather than tight writing. There is no front-loaded explanation of what the tool returns or how to call it.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 7-parameter tool with no annotations, no output schema, and no parameter documentation, two words are wholly inadequate. An agent cannot reliably invoke this tool from the given information.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Seven parameters with 0% schema description coverage and the description adds nothing. Names like 'service', 'confirm', 'token', and the lat/lng pairs are left entirely unexplained, forcing the agent to guess at types, requiredness, and meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description '(dry-run)' plus 'Flexi quote' essentially restates the tool name ride_flexi with a hint that it simulates a fare quote. It gives no verb explaining what is produced or how it differs from siblings like ride_price, ride_options_quote, or ride_request.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus the many sibling quote/price/request tools. The only inference an agent can draw is from the parenthetical '(dry-run)', which is not an explicit usage condition.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.