milano-mobility-mcp

Overview Schema Source Related Servers Discussions Admin

query_movein_allowance

Read-onlyIdempotent

Check MoVe-In budget allowance by subtracting driven kilometers from the annual limit and evaluating a trip distance against the remaining balance.

Instructions

Sottrae km dichiarati con Decimal; NON saldo autenticato né autorizzazione alla circolazione.

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": "query_movein_allowance"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Default
`rule`	No	Sola sottrazione e confronto sui tre valori dichiarati; nessuna formula normativa.
`reasons`	Yes
`decision`	No	non_determinabile
`km_residui`	Yes
`km_percorsi`	Yes
`km_eccedenti`	Yes
`source_checks`	No
`soglia_annuale`	Yes
`distanza_viaggio`	Yes
`input_provenance`	No	user_unverified
`calculation_status`	No	calcolato
`authenticated_balance`	No
`km_residui_dopo_viaggio`	Yes
`km_eccedenti_dopo_viaggio`	Yes
`viaggio_nel_budget_dichiarato`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already mark the tool read-only and non-destructive; the description adds useful behavioral context beyond that: Decimal-based arithmetic rather than floating point, and a clear disclaimer that this is not an authenticated balance nor an authorization check. No contradiction with the annotations.

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?

The description is two short sentences with the core computation front-loaded and the important misuse caveat isolated in the second sentence. Every word earns its place; there is no filler or unnecessary repetition.

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

Completeness3/5

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

For a small read-only computational query with an output schema, the main caveat is present. However, the role of all three request fields and the exact subtraction source are not fully specified, so the agent may still have to infer the formula from parameter names.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only loosely references 'km dichiarati' and Decimal precision. It does not explain soglia_annuale or distanza_viaggio, nor how they relate to the subtraction, so an agent cannot fully determine parameter semantics from the description alone.

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 states a specific operation: subtract declared km using Decimal precision, and explicitly rules out authenticated balance and circulation authorization. This distinguishes it from access/authorization tools, though the exact meaning of 'move-in allowance' is still partly left to the tool name.

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

Usage Guidelines3/5

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

The description gives implied usage guidance by saying it is NOT an authenticated balance or a circulation authorization, which helps prevent misuse for access decisions. However, it does not explicitly state when to use this tool or name sibling tools as alternatives.

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

Deploy Server