Skip to main content
Glama

calcular_kilometraje

Read-only

Calcula la compensación o deducción fiscal por uso de vehículo propio en actividades económicas. Para empleados: exención IRPF hasta 0,26 €/km (Art. 9.A.2.b RIRPF, cuantía revisada por la Orden HFP/792/2023 (BOE-A-2023-16461)). Para autónomos: deducción en IRPF e IVA según exclusividad del uso del vehículo. Encadenable con calcular_irpf, calcular_cuota_autonomo, comparar_autonomo_vs_sl. Ideal para: "¿Cuánto me puedo deducir por usar el coche en el trabajo?" o "Mi empresa me paga 0,20€/km, ¿es correcto?"

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": {
      "perfil": "<perfil>",
      "kmProfesionalesAnuales": "<kmProfesionalesAnuales>"
    },
    "name": "calcular_kilometraje"
  }
}

Input Schema

NameRequiredDescriptionDefault
perfilYes"empleado" = trabajador por cuenta ajena. "autonomo" = autónomo o profesional.
costeRealPorKmNoCoste real del vehículo por km (combustible, amortización, seguro, etc.) en euros. Por defecto 0,20 €/km.
tipoMarginalIRPFNoTipo marginal IRPF para calcular el ahorro fiscal en porcentaje. Por defecto 30%.
totalGastosVehiculoNoPara autónomos: total de gastos del vehículo en el año (combustible, seguro, reparaciones, amortización) en euros.
usoExclusivoActividadNoPara autónomos: ¿el vehículo está afecto exclusivamente a la actividad? (difícil de acreditar para turismos). Por defecto false.
kmProfesionalesAnualesYesKilómetros profesionales anuales (desplazamientos laborales o de la actividad económica).
compensacionRecibidaPorKmNoPara empleados: compensación que paga la empresa por km en euros. Por defecto 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint=true already declaring safe operation, the description adds valuable legal context: the 0,26 €/km exemption for employees, IRPF/IVA treatment for autónomos, and the importance of vehicle exclusivity. It still doesn't describe the return value format, but given annotations and the calculator nature, the added behavioral detail is solid.

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?

The description front-loads the core purpose, then layers legal references, chaining options, and example queries without wasted words. It is dense but appropriately structured for a tax-related calculator.

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 7-parameter, no-output-schema tool, the description covers legal basis, use cases, chaining, and default behaviors implicitly. It is nearly complete, but the absence of any statement about the return value (e.g., annual compensation amount) leaves a minor gap.

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 fully documents each parameter. The description provides conceptual context (legal limits, exclusivity) but adds no parameter-specific syntax or format details beyond what the schema supplies, so the baseline 3 is appropriate.

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 names a specific verb (calcula) and resource (compensación/deducción fiscal por uso de vehículo propio) and grounds it in a distinct legal/tax domain. This makes it easily separable from siblings like calcular_combustible or recomendar_vehiculo despite not naming them explicitly.

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 provides clear ideal use cases (e.g., '¿Cuánto me puedo deducir por usar el coche?') and mentions chaining with related tools, giving strong contextual guidance. However, it does not state explicit exclusions or when to choose an alternative sibling, so it falls short of 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