Skip to main content
Glama

Cuánto te queda en tu ISA

calcular_isa
Read-onlyIdempotent

Calcula cuánto te queda por meter en tus ISAs este año fiscal (límite de £20,000), los días hasta el 5 de abril y cuánto al mes para llenarlo.

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

Input Schema

NameRequiredDescriptionDefault
aportadoNoLo que ya has metido en ISAs desde el 6 de abril, en libras.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value by disclosing the returned quantities (remaining allowance, days to deadline, monthly saving needed) in the absence of an output schema. It does not disclose caveats such as whether the calculation ignores ISA type splits or prior-year transfers.

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?

A single front-loaded sentence with the verb, the scope and the outputs packed in without filler. Every clause contributes information an agent needs.

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 one-parameter, annotation-covered calculator with no output schema, the description does the necessary work by stating the three results and the fiscal-year basis. Minor gaps remain: it does not clarify whether other ISA types or transfers are factored in, or that the result is UK-tax-year specific beyond the £ symbol.

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?

The single parameter is fully documented in the schema (amount contributed since 6 April, in pounds, non-negative, default 0), so the schema carries the burden. The description only indirectly frames it by saying it computes what remains to contribute this year, which confirms the subtraction logic but adds no format or edge-case detail beyond the schema.

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 uses a specific verb ('Calcula') plus a concrete resource and scope: remaining ISA allowance for 'este año fiscal' with the £20,000 limit named. It also enumerates the three computed outputs (remaining amount, days to 5 April, monthly amount), so the agent knows exactly what comes back. It does not name or differentiate against any sibling, though none of the listed siblings (calcular_nomina, calcular_vivienda, comparar_sueldos) competes for the same intent.

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?

Usage is implied rather than stated: the mention of 'año fiscal', the £20,000 cap and 5 April implicitly scope this to UK ISA allowance planning, which is enough for an agent to place it. There is no explicit when-to-use/when-not guidance and no reference to alternative tools, even for near-neighbours like the other calcular_* tools.

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