Skip to main content
Glama

Loan payment

loan_payment
Read-onlyIdempotent

The monthly payment, total interest and total paid on a car loan from the amount financed, APR and term, with what a term over 60 months adds in interest compared with 60. Use it for a loan on its own; out_the_door works the payment from a car price, and refinance_check compares a new loan with an existing one.

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": {
      "amount": "<amount>",
      "apr": "<apr>",
      "term_months": "<term_months>"
    },
    "name": "loan_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
aprYesAPR in percent (6.49 means 6.49%)
amountYesAmount financed: the out-the-door price less the down payment and trade equity
term_monthsYesLoan term in months, like 60

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"Amount financed"New value: +"Amount financed: the out-the-door price less the down payment and trade equity"
    • changedInput schema / properties / apr / description
      Previous value: -"APR in percent"New value: +"APR in percent (6.49 means 6.49%)"
    • changedInput schema / properties / term_months / description
      Previous value: -"Term in months"New value: +"Loan term in months, like 60"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds real substance by disclosing the computed outputs, including a bonus comparison of terms over 60 months versus 60. It does not mention bounds handling (APR up to 40, term up to 120) or rounding, but for a stateless calculator that disclosure is not critical.

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?

Two sentences, front-loaded with what the caller gets before the routing guidance. The trailing clause about the over-60-month comparison is slightly clunky but carries information found nowhere else, so nothing is truly wasted.

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

Completeness5/5

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

With no output schema, the description compensates fully by enumerating the return values. All three required parameters are schema-documented and the sibling landscape is addressed, leaving nothing an agent needs in order to call this correctly.

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 each parameter already carries a precise definition, including that amount is the out-the-door price less down payment and trade equity. The description reinforces the three inputs as the loan definition but adds no format, unit or constraint detail beyond the schema, so the baseline 3 applies.

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?

Names the exact resource and outputs: monthly payment, total interest and total paid on a car loan, computed from amount financed, APR and term. The second sentence explicitly distinguishes it from out_the_door (payment from a car price) and refinance_check (compare against an existing loan), so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit use condition ("for a loan on its own") plus two named alternatives with the condition that selects each: out_the_door when starting from a car price, refinance_check when comparing to an existing loan. No inference required.

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