Skip to main content
Glama

Drivaron driver income calculator

How much do you really earn?

estimate_driver_income
Read-onlyIdempotent

Net income calculator for ride-hail drivers (Uber, inDrive, DiDi, Cabify, Yango) in Colombia, Peru and Bolivia: from earnings, hours and costs (fuel, commission, car rent) it gives net income per day, week and month, net per hour, and how it compares with the city's typical target. Use it when a driver asks how much they make, whether driving pays, or how to compare apps or shifts.

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": {
      "earnings": "<earnings>",
      "hours": "<hours>"
    },
    "name": "estimate_driver_income"
  }
}

Input Schema

NameRequiredDescriptionDefault
kmNoKm driven in the period, for fuel and cost per km.
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.
langNoLanguage of the summary: es (default) or en.
hoursYesHours worked in that period (online time).
periodNoPeriod of earnings and hours: day (default), week or month.
countryNoCountry when the city is unknown: Colombia (CO, COP), Peru (PE, PEN) or Bolivia (BO, BOB).
currencyNoCurrency, when neither city nor country is known.
earningsYesEarnings in the period from the apps, in local currency.
fuel_costNoTotal fuel spent in the period.
fuel_priceNoFuel price per gallon or liter (used with km and km_per_fuel_unit).
other_costsNoOther costs in the period: car rent, maintenance, phone plan, parking.
days_per_weekNoDays worked per week, to project week and month. Default 6.
commission_pctNoCommission in % still to subtract, if earnings are before commission. Default 0.
fuel_cost_per_kmNoFuel cost per km (used with km).
km_per_fuel_unitNoKm the car drives per gallon or liter of the fuel_price unit.

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds meaningful behavior beyond that: it discloses the calculation chain (earnings − fuel − commission − car rent) and, importantly, that it benchmarks against 'the city's typical target', which is non-obvious output behavior. It does not disclose that the target is a heuristic default or how defaults are applied, keeping it below 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?

Front-loaded with the purpose and output set in the first sentence, with the usage trigger isolated in a short second sentence. No filler, no repetition of the title, and no restatement of annotation flags.

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?

With an output schema present, return values need not be explained, and the description correctly focuses on inputs, supported regions and the benchmark comparison. For a 15-parameter tool it is nearly complete, though it could briefly note that missing city/country/currency inputs fall back through defaults and that the 'typical target' is an assumption rather than ground truth.

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%, so the schema already documents every parameter including enums, defaults and units; baseline is 3. The description groups inputs conceptually ('earnings, hours and costs (fuel, commission, car rent)'), which signals the required core versus optional cost inputs, but adds no syntax, unit or mutual-exclusivity detail beyond the schema (e.g. km+fuel_price vs fuel_cost_per_km).

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?

The description uses a concrete verb and resource ('Net income calculator for ride-hail drivers') and enumerates the platforms (Uber, inDrive, DiDi, Cabify, Yango) and geographies (Colombia, Peru, Bolivia). It goes on to state the exact outputs — net income per day/week/month, net per hour, and comparison against the city's typical target — which lets an agent distinguish this estimator from a market-lookup or offer-grading sibling without opening the schema.

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?

It gives three explicit triggering situations ('when a driver asks how much they make, whether driving pays, or how to compare apps or shifts'), which is clear positive guidance. It stops short of naming when not to use it or pointing to a specific sibling, so a 4 rather than a 5.

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