Skip to main content
Glama
OpenLMNP

OpenLMNP

Get Income

get_income
Read-only

Retrieve full details of a rental income entry by its ID, including amounts, VAT, platform fees, tourist tax, booking and traveler information.

Instructions

Retourne le détail complet d'une recette locative par son identifiant : montants TTC/HT, TVA, frais de plateforme, taxe de séjour, informations de réservation et du voyageur.

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": {
      "income_id": "<income_id>"
    },
    "name": "get_income"
  }
}

Input Schema

NameRequiredDescriptionDefault
income_idYesIdentifiant de la recette

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / income_id / description
      Added value: +"Identifiant de la recette"
  2. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes the safety profile, so the description's main added value is disclosing exactly what comes back (amounts TTC/HT, TVA, platform fees, tourist tax, booking and traveler data). This is real behavioral context given that no output schema exists. It does not cover failure behavior for an invalid identifier, which keeps it from a 5.

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?

One front-loaded sentence that leads with the action and resource, then enumerates return fields. The field list is long but each item is informative rather than filler, so the sentence earns its length.

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, the definition covers the action, the key, and the returned data, compensating for the absent output schema. The only real gap is what happens when the identifier does not match any record.

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?

There is a single required parameter with 100% schema description coverage ('Identifiant de la recette'), so the schema already carries the load. The description only echoes that the identifier selects the record and adds no format, range, or sourcing guidance beyond the schema.

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 ('Retourne') and resource ('le détail complet d'une recette locative') with the lookup key ('par son identifiant'). It clearly separates this from write siblings such as create_income or delete_income, though it does not name any sibling explicitly.

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?

Usage is only implied: fetch a single income record when you already hold its identifier. There is no statement of when to prefer this over get_dashboard_summary or get_projection, and no prerequisites or when-not conditions are given.

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