Skip to main content
Glama

Comparar dos sueldos en UK

comparar_sueldos
Read-onlyIdempotent

Compara el neto de dos sueldos u ofertas en UK: distinto salario, país (p. ej. Londres frente a Edimburgo), pensión o año fiscal. Devuelve el neto mensual de cada uno y la diferencia.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "comparar_sueldos"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesPrimer sueldo (mismos campos que calcular_nomina).
bYesSegundo sueldo (mismos campos que calcular_nomina).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the output shape (net for each and the difference), but says nothing about caveats such as mixed fiscal years between a and b, currency, or rounding. Adequate, not rich.

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?

Two sentences, zero waste, with the core comparison stated first and the return value second. Nothing is repeated from the schema and nothing could be cut without losing meaning.

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 two-object, deeply nested tool with no output schema, the description covers purpose and result shape and the schema carries the field semantics. The only gap is behavioural detail on edge cases (e.g. differing fiscal years across a and b), which would make it complete.

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% and both nested objects document every field thoroughly, so the baseline is 3. The description adds only a light hint that salary, country, pension and fiscal year can vary between the two entries, which loosely maps to the parameter groups but adds no syntax or format detail.

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?

States a specific verb and resource ("Compara el neto de dos sueldos u ofertas en UK") and even summarises the return value (monthly net for each plus the difference). It implicitly separates itself from calcular_nomina via the two-input framing, but never names the sibling or makes the distinction explicit.

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 list of dimensions that can differ (salary, country, pension, fiscal year) implies the comparison use case, so the agent can infer when this applies. However, there is no explicit when-to-use versus calcular_nomina (single salary) or when-not guidance, leaving the routing decision to inference.

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