Calcula el sueldo neto (mensual y anual), la retención de IRPF y la cotización a la Seguridad Social a partir del salario bruto anual. Para una consulta general usa mejor "consulta_nomina".
| Name | Required | Description | Default |
|---|---|---|---|
| pagas | No | Pagas al año: 12 o 14. Por defecto 14. | |
| num_hijos | No | Número de hijos. Por defecto 0. | |
| situacion_familiar | No | Situación familiar. Por defecto "soltero". | |
| salario_bruto_anual | Yes | Salario bruto anual en euros |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description reveals that the tool computes net salary, IRPF withholding, and Social Security contributions. The annotation readOnlyHint=true is consistent with a calculation tool. The description adds detail about the outputs beyond the annotation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of two concise sentences. The first states the purpose, and the second provides usage guidance. No extraneous information; every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that there is no output schema, the description adequately explains what the tool returns (monthly and annual net salary, IRPF withholding, Social Security). It also mentions an alternative tool. It could perhaps specify the tax jurisdiction, but the context implicitly indicates Spanish tax system.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 all parameters. The description does not add additional parameter-specific details beyond what the schema provides. Baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it 'calcula el sueldo neto (mensual y anual), la retención de IRPF y la cotización a la Seguridad Social' from annual gross salary. It also distinguishes itself from the sibling 'consulta_nomina' by suggesting that tool for general queries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells when to use this tool vs the alternative 'consulta_nomina' ('Para una consulta general usa mejor "consulta_nomina"'). No further exclusions or prerequisites are given, but the guidance is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
There are many tools with overlapping domains (e.g., multiple retirement calculators, home buying calculators), but detailed descriptions and explicit guidance on when to use comprehensive vs. specific tools help clarify. However, the sheer number (49) still creates potential confusion for an agent.
All tools follow a consistent convention: infinitive verb or noun prefix (calcular, comparar, consulta) followed by descriptive noun phrase in snake_case. No mixed styles or irregularities.
49 tools is high but justifiable given the broad scope of Spanish financial/legal calculations. It leans toward the heavy side but remains within a manageable range for a comprehensive server.
The tool set covers a wide spectrum of personal finance: income, taxes, housing, inheritance, self-employment, investments, etc. Only minor gaps exist (e.g., no separate tool for rental income beyond the alquiler tools, but included in IRPF).
