Skip to main content
Glama

dev_tools_loan_calculate

[$x402 pago por llamada] Calcula la cuota fija mensual de un préstamo con amortización estándar.

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": {
      "principal": "<principal>",
      "annual_rate_percent": "<annual_rate_percent>",
      "term_months": "<term_months>"
    },
    "name": "dev_tools_loan_calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
principalYes
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.
term_monthsYes
annual_rate_percentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It does add one genuinely useful behavioral fact — the [$x402 paid per call] tag signals a payment requirement — but says nothing about rate compounding convention, rounding of the result, or behavior on edge inputs like a zero rate, all of which materially change the computed answer.

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?

A single compact sentence with the cost tag front-loaded and the purpose immediately following; nothing is wasted. It is arguably too terse for the gaps it leaves, but the brevity itself is well structured.

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

Completeness2/5

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

For a three-parameter numeric calculation with no annotations and no output schema, the description is thin. The return value is inferrable (monthly payment), but the amortization convention — the one thing that determines whether the number is correct — is left entirely undefined.

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 only 25%: x_payment is documented, while principal, annual_rate_percent, and term_months have no descriptions in either the schema or the description. The names hint at units (percent, months), but the description never clarifies whether the rate is nominal annual or effective, how many payments per year, or whether the output is rounded.

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 — calculates the fixed monthly payment of a loan under standard amortization — which cleanly separates it from the generic sibling dev_tools_calculate. The domain specificity makes the intent unmistakable, though it doesn't name a sibling to contrast with explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus dev_tools_calculate or what conditions apply (e.g. only for fixed-rate fully-amortizing loans). The only contextual note is that a call costs money via x402, which is a billing fact rather than usage direction.

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