Skip to main content
Glama
OpenLMNP

OpenLMNP

Get Loan Schedule

get_loan_schedule
Read-only

Returns the full loan amortization schedule, optionally filtered by year, with repayment, interest, insurance, total, and remaining balance per installment plus period totals.

Instructions

Retourne le tableau d'amortissement complet d'un emprunt avec filtre optionnel par année. Chaque ligne contient : numéro d'échéance, date, capital remboursé, intérêts, assurance, total et capital restant dû. Inclut les totaux de la période.

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": {
      "loan_id": "<loan_id>"
    },
    "name": "get_loan_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoFiltrer par année, ex: 2024 (optionnel — retourne tout le tableau si absent)
loan_idYesIdentifiant de l'emprunt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • addedInput schema / properties / loan_id / description
      Added value: +"Identifiant de l'emprunt"
    • addedInput schema / properties / year / description
      Added value: +"Filtrer par année, ex: 2024 (optionnel — retourne tout le tableau si absent)"
  2. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

readOnlyHint=true already establishes this is a safe read, but the description goes further by disclosing the shape of the response: installment number, date, principal, interest, insurance, total, remaining principal, plus period totals. Since no output schema exists, this return-content disclosure is the main behavioral value the description adds.

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, each earning its place: the first gives the purpose and the optional filter up front, the second enumerates the returned columns. No filler, no repetition of the tool name or title.

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?

With no output schema, the description carries the burden of describing return values, and it does so concretely by listing every row field and the period totals. Minor gaps remain: nothing about ordering, whether future installments are included, or result size for long loans.

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 the schema already explains that year is optional and returns the whole table when absent. The description only restates that a year filter is optional, adding no format, range, or edge-case detail beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: it returns a loan's full amortization schedule, with an optional year filter, and even enumerates the row fields. It is clear about what the tool produces, but it never contrasts itself with the sibling compute_loan_schedule, so an agent must still infer whether this retrieves a stored schedule or triggers a computation.

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 when-to-use or when-not-to-use guidance and no mention of alternatives, despite the presence of closely related siblings such as compute_loan_schedule and get_loan. The only conditional guidance concerns the optional year parameter, which is parameter behavior rather than tool-selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.