Skip to main content
Glama

Drivaron driver income calculator

Targets by city

get_market_defaults
Read-onlyIdempotent

Starting hourly targets, average speeds and per-km floors per city for ride-hail drivers (Uber, inDrive, DiDi, Cabify, Yango) in Colombia, Peru and Bolivia, with the apps that operate there. Use it for typical numbers before grading an offer or estimating income.

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_market_defaults"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the summary: es (default) or en.
countryNoColombia, Peru or Bolivia (name, CO/PE/BO or currency). Empty for all.

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is fully covered. The description adds content scope (which apps and metrics are included) but says nothing about data freshness or how current the targets are, which is the main behavioral risk for a reference-data tool. An output schema exists, so silence on return shape is acceptable.

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 tight sentences, front-loaded with the payload and ending with the intended use, with no filler. Slightly list-heavy phrasing but every clause conveys scope.

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 simple read-only, zero-required-parameter lookup with an output schema and full schema coverage, the description supplies what is needed: what data, which regions, which apps, which metrics. The only real gap is not noting whether the targets are periodically refreshed.

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 coverage is 100%, including the accepted country formats (name, CO/PE/BO, currency) and the es/en enum, so the schema carries the parameter meaning. The description corroborates the country scope but adds no new semantics and never mentions the language parameter.

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?

The description names a concrete resource (starting hourly targets, average speeds, per-km floors per city) and scope (Colombia, Peru, Bolivia, five named ride-hail apps), so an agent knows exactly what data comes back. It lacks an explicit verb like 'returns' and only indirectly separates itself from estimate_driver_income and grade_ride_offer.

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?

'Use it for typical numbers before grading an offer or estimating income' gives clear situational guidance that positions this as the baseline-lookup step preceding the sibling tools. It does not state when the tool is unnecessary (e.g. outside the three countries) or name the alternatives explicitly.

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