Skip to main content
Glama

Drivaron driver income calculator

Is this trip worth it?

grade_ride_offer
Read-onlyIdempotent

Grade one trip offer for ride-hail drivers (Uber, inDrive, DiDi, Cabify, Yango) in Colombia, Peru and Bolivia, the way the Drivaron app does: pay per km and per hour with the pickup included, an A+/A/B/C grade against the driver's hourly target, and the minimum fare to ask for (inDrive counteroffer floor). Use it when a driver asks whether an offer is worth taking or what to charge.

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": {
      "fare": "<fare>",
      "trip_km": "<trip_km>"
    },
    "name": "grade_ride_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
tipNoTip or bonus included with the offer.
cityNoCity, which sets currency, starting hourly target and average speed. One of: Bogotá, Medellín, Cali, Barranquilla, Lima, Arequipa, Trujillo, Santa Cruz de la Sierra, La Paz, Cochabamba.
fareYesFare shown in the offer, in local currency (e.g. 14000 COP, 14 PEN, 28 BOB).
langNoLanguage of the summary: es (default) or en.
countryNoCountry when the city is unknown: Colombia (CO, COP), Peru (PE, PEN) or Bolivia (BO, BOB).
trip_kmYesTrip distance in km (pickup point to destination).
currencyNoCurrency, when neither city nor country is known.
trip_minNoTrip duration in minutes, if the offer shows it. Otherwise estimated from speed.
pickup_kmNoDistance to the passenger in km. Unpaid, so it lowers real pay per km.
speed_kmhNoAverage city speed in km/h. Defaults to the city's value.
pickup_minNoMinutes to reach the passenger, if shown. Otherwise estimated from speed.
commission_pctNoPlatform commission in % taken from the fare, if the fare shown is before commission (e.g. 10 for inDrive). Default 0.
target_per_hourNoDriver's hourly earnings goal in local currency. Defaults to the city's starting target.
fuel_cost_per_kmNoFuel cost per km, to show profit after fuel.

Output Schema

NameRequiredDescriptionDefault
appYesThe Drivaron app and its Play download link.
toolYes
colorNogreen, yellow or red for offers.
notesNoAssumptions made for missing inputs.
resultYesAll numbers, raw and formatted in local currency.
summaryYesOne-paragraph answer in the requested language, ready to show the driver.
result_pageNoShareable page with this result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses the computation model (pickup included in pay per km/hour), the grading scheme, and the inDrive counteroffer-floor output. It doesn't explain default resolution (city vs country vs currency) or that missing durations are estimated from speed, but the latter is in the schema.

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?

Two sentences, with the purpose and output set front-loaded before the usage trigger. The first sentence is dense with parenthetical platform and output lists but every element is load-bearing; nothing is filler.

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 14-parameter, deterministic calculation tool with an output schema and rich annotations, the description supplies the domain model, geography and intended outputs. The remaining complexity (defaults cascading from city to country to currency, speed/duration estimation) is fully documented in the schema, so little 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 100%, so the baseline is 3, and the description earns an increment by explaining why unpaid pickup distance lowers real pay and what the minimum-fare output represents. It does not walk through the 14 parameters or the city/country/currency fallback chain, which remains schema-only knowledge.

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 ('Grade one trip offer') plus the exact outputs returned: pay per km and per hour, an A+/A/B/C grade against the hourly target, and a minimum fare to ask for. It also scopes the domain (ride-hail drivers, five named platforms, Colombia/Peru/Bolivia), so an agent can tell it apart from a generic income estimator.

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 an explicit trigger: 'Use it when a driver asks whether an offer is worth taking or what to charge.' That maps the tool to a recognizable user intent. It does not state when NOT to use it or contrast it with the available siblings (estimate_driver_income, get_market_defaults), so the agent must infer the boundary.

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