Skip to main content
Glama
OpenLMNP

OpenLMNP

Get Loan

get_loan
Read-only

Retrieve a real estate loan’s full details and financial summary—principal, rate, term, monthly payment, insurance, fees, total cost, and current-year interest and insurance.

Instructions

Retourne le détail complet d'un emprunt immobilier avec un résumé financier : capital, taux, durée, mensualité, assurance, frais d'emprunt, coût total, intérêts et assurances de l'année courante.

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

Input Schema

NameRequiredDescriptionDefault
loan_idYesIdentifiant de l'emprunt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / loan_id / description
      Added value: +"Identifiant de l'emprunt"
  2. First observedv0.1.1

TDQS

A3.5/5.0
Behavior4/5

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

The readOnlyHint=true annotation already establishes the safety profile, and the description goes beyond it by detailing the returned content, including the derived year-to-date interest and insurance figures ('intérêts et assurances de l'année courante'), which is genuinely useful context with no output schema present. It stops short of covering error behavior for an unknown loan_id or any access constraints.

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 front-loaded sentence: purpose first, then the enumerated fields. The field list is long but each item conveys real return content rather than padding.

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 read tool with annotations and no output schema, the description supplies the return-value picture the schema cannot, so an agent can call it correctly. The only missing element is a pointer to the schedule tools for time-series detail.

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 single parameter loan_id is documented as 'Identifiant de l'emprunt'. The description adds no format, range, or sourcing detail beyond that, so the schema carries the load and 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 uses a specific verb and resource ('Retourne le détail complet d'un emprunt immobilier') and enumerates the financial fields returned (capital, taux, durée, mensualité, assurance, frais, coût total), so an agent knows exactly what it gets. It does not explicitly distinguish itself from get_loan_schedule or compute_loan_schedule, though the 'résumé financier' framing implies a summary rather than an amortization schedule.

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 guidance, no stated prerequisites, and no mention of alternatives such as the schedule tools. Usage is only implied by the required loan_id, leaving the agent to infer that this is the lookup for a single loan's financial summary.

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