Skip to main content
Glama

mcp-livedatapro

by site.livedatapro
OverviewDiscussionsAdmin

getTaxiEstimate

Calculate real-time taxi, Uber, and airport transfer fares, surge multipliers, and travel time in traffic. Use when calculating point-to-point street ride-hailing (Uber, Lyft) or metered taxi fare ranges, surge multipliers, and live traffic duration. Do not use for scheduled public transit/trains (use getTransitSchedule) or parcel courier shipping (use getCourierShippingRates). Computes live routing and returns min/max USD quotes across vehicle classes.

Input Schema

NameRequiredDescriptionDefault
pickup_addressYesFull pickup street address, GPS coordinates (lat,lon), or 3-letter airport IATA code.
dropoff_addressYesFull dropoff street address, GPS coordinates (lat,lon), or destination landmark/hotel name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / dropoff_address / examples
      Added value: +[
+  "10 Downing St, London SW1A 2AA"
+]
    • addedInput schema / properties / dropoff_address / minLength
      Added value: +3
    • addedInput schema / properties / pickup_address / examples
      Added value: +[
+  "LHR Terminal 5, London"
+]
    • addedInput schema / properties / pickup_address / minLength
      Added value: +3
  2. Changed2 schema fields changed
    • changedInput schema / properties / dropoff_address / description
      Previous value: -"Dropoff street address, coordinates, or hotel name"New value: +"Full dropoff street address, GPS coordinates (lat,lon), or destination landmark/hotel name."
    • changedInput schema / properties / pickup_address / description
      Previous value: -"Pickup street address, coordinates, or airport code"New value: +"Full pickup street address, GPS coordinates (lat,lon), or 3-letter airport IATA code."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden; it discloses that pricing is real-time with surge multipliers, that routing is computed live, and that the response is min/max USD quotes per vehicle class. It stops short of noting rate limits, coverage limits, or what happens when a route cannot be computed, which keeps it off a 5.

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 front-loaded sentences: capability, then routing guidance, then return shape. Every sentence carries distinct information with no repetition of the title or schema.

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?

There is no output schema, and the description compensates by stating the return shape (min/max USD quotes across vehicle classes). With only two fully documented parameters and clear sibling routing, an agent has everything needed to call it correctly.

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 both parameters are fully documented in the schema (address, lat/lon, or IATA code). The description only implies point-to-point inputs and adds no format or constraint detail beyond the schema, so baseline 3 applies.

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+resource: calculates real-time taxi/Uber/airport-transfer fares, surge multipliers, and traffic travel time. It names the sibling alternatives it is not (getTransitSchedule, getCourierShippingRates), so an agent can route between them without opening schemas.

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

Usage Guidelines5/5

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

Explicit when-to-use (point-to-point street ride-hailing or metered taxi fare ranges, surge, live traffic duration) and explicit when-not-to-use, each with a named alternative tool. Nothing is left to inference.

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

All mcp-livedatapro toolsInspect
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