Skip to main content
Glama

any.cab

Rate card

get_rates
Read-onlyIdempotent

Per-km rate card for each vehicle on a date (EUR): base_cost, per_km, max_pax and luggage. price = base_cost + driving distance in km × per_km, minimum €20.00 per trip. Indicative only: an exact, bookable price depends on the driving distance of the trip.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoTrip date YYYY-MM-DD (Malta). Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral value on top: the exact pricing formula, a €20.00 minimum per trip, and the caveat that results are indicative and not bookable. Only the default-date behavior and any rate validity/refresh expectations are left unstated.

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 compact sentences: the resource and returned fields first, then the pricing formula and floor, then the accuracy caveat. Nothing is repeated for padding and the ordering puts the most actionable information up front.

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 one-parameter read tool with no output schema, the description does the heavy lifting by naming the four returned fields, the formula and the minimum charge. What it omits is how each vehicle is identified in the response (name or id) and whether rates can vary by season beyond the date — minor gaps that would matter for multi-vehicle comparison.

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 100% and the single parameter already documents the YYYY-MM-DD format, the Malta timezone caveat and the today-default. The description only restates "on a date," adding no new constraint or format detail. Baseline 3 is appropriate when the schema carries the parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Per-km rate card for each vehicle on a date (EUR)" names the resource (rate card), the dimension it varies on (vehicle), and the scope (date). It also enumerates the returned fields (base_cost, per_km, max_pax, luggage), so an agent knows exactly what it gets. It stops short of explicitly contrasting itself with the pricing sibling (get_quote), which keeps it off a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

"Indicative only: an exact, bookable price depends on the driving distance of the trip" signals the tool is for estimation and that something else is needed for a firm price, which is a useful implied boundary. However, no alternative tool is named and no condition is given for when to call this versus get_quote or create_booking, so the routing must be inferred.

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