milano-mobility-mcp

Overview Schema Source Related Servers Discussions Admin

get_daily_costs

Read-onlyIdempotent

Retrieve daily access costs for Milan's Area B and Area C by selecting area, tariff, and date, to calculate vehicle entry fees and manage mobility budgets.

Instructions

Nessuna tariffa/scadenza abilitata nel catalogo attuale: importi null, mai zero implicito.

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": {
      "request": "<request>"
    },
    "name": "get_daily_costs"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Default
`area`	Yes
`on_date`	Yes
`reasons`	Yes
`currency`	No	EUR
`decision`	No	non_determinabile
`evidence`	Yes
`evaluated_at`	Yes
`source_checks`	No
`total_due_eur`	No
`calculation_status`	Yes
`ordinary_ticket_eur`	No
`activation_deadline_exclusive`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

C2.4/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructve safety, so the description only needs to add behavioral context. It does so by warning that missing amounts are null, not zero, which prevents a common misinterpretation. This is useful, though it could be more explicit about what triggers the condition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no padding, so it is concise. However, it is structurally mislead: it front-loads a niche response caveat and omits the primary operation entirely, which makes the terseness a defect rather than a virtue.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Rich annotations and a self-describing input schema cover safety and parameter names, but the description leaves out the tool's core purpose and usage context. The null caveat is valuable but cannot make the overall definition complete for an agent deciding whether to call this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description contains no information about request, area, on_date, or tariff. The input schema's names and enums carry all meaning; the description adds nothing and does not compensate for the low coverage.

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

Purpose2/5

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

The description never states that this tool retrieves daily costs; it only says that with no enabled tariff/expiration in the current catalog, amounts are null and never implicit zero. The action and resource are left entirely to the tool name. This is not a pure tautology, but it is missing a clear purpose statement.

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

Usage Guidelines2/5

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

There is no guidance on when to call get_daily_costs rather than check_vehicle_access, query_movein_allownce, or get_active_smog_level. The single sentence is a catalog-state caveat, not a usage condition or alternative-routing rule.

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

Deploy Server