Skip to main content
Glama
OpenLMNP

OpenLMNP

List Loans

list_loans
Read-only

Retrieve real estate loans with optional property filter, showing bank, capital, rate, duration, monthly payment, insurance, dates, and total estimated cost.

Instructions

Liste les emprunts immobiliers de l'utilisateur avec filtre optionnel par bien. Retourne pour chaque emprunt : banque, capital, taux, durée, mensualité, assurance, dates de début/fin et coût total estimé.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_loans"
  }
}

Input Schema

NameRequiredDescriptionDefault
property_idNoFiltrer par identifiant de bien (optionnel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / property_id / description
      Added value: +"Filtrer par identifiant de bien (optionnel)"
  2. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this as a safe read operation, so the description only needs to add context. It does add value by enumerating the returned fields (bank, capital, rate, duration, monthly payment, insurance, dates, total cost), effectively compensating for the absent output schema. It says nothing about ordering, pagination, or scope limits, so it earns a solid but not exceptional score.

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, no filler: the first front-loads what is listed and the filter, the second enumerates return fields that would otherwise be unknown. Every clause carries information the agent cannot get from structured fields.

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 simple one-parameter read tool with annotations and no output schema, the description covers purpose, filtering, and return contents well. The only gaps are minor operational details such as result ordering or whether all loans are returned by default.

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?

With a single optional parameter at 100% schema coverage, the schema already documents property_id fully. The description restates the optional property filter without adding format or behavioral detail, which is the expected baseline when the schema does the work.

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 names a specific verb and resource ('Liste les emprunts immobiliers') and states the optional filter by property, so the agent knows exactly what it retrieves. It does not explicitly contrast with sibling tools such as compute_loan_schedule, but the resource is distinct enough to be unambiguous.

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 phrase 'avec filtre optionnel par bien' implies when the property_id parameter is relevant, which is useful usage context. However, there is no explicit statement of when to prefer this over compute_loan_schedule or how it relates to list_properties, so guidance remains implied rather than stated.

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