Skip to main content
Glama
OpenLMNP

OpenLMNP

List Incomes

list_incomes
Read-only

Retrieves rental income records for French LMNP tax reporting with optional filters by property, year, and platform, returning euro amounts including VAT, platform fees, and tourist tax.

Instructions

Liste les recettes locatives de l'utilisateur avec filtres optionnels par bien, année et plateforme (airbnb, booking, abritel, direct, other). Retourne les montants en euros avec TVA, frais de plateforme et taxe de séjour.

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

Input Schema

NameRequiredDescriptionDefault
yearNoFiltrer par année fiscale, ex: 2024 (optionnel)
sourceNoFiltrer par plateforme : airbnb, booking, abritel, direct, other (optionnel)
property_idNoFiltrer par identifiant de bien (optionnel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.1
    • addedInput schema / properties / property_id / description
      Added value: +"Filtrer par identifiant de bien (optionnel)"
    • addedInput schema / properties / source / description
      Added value: +"Filtrer par plateforme : airbnb, booking, abritel, direct, other (optionnel)"
    • addedInput schema / properties / year / description
      Added value: +"Filtrer par année fiscale, ex: 2024 (optionnel)"
  2. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the description is not required to repeat it. It adds real value beyond that by disclosing what the returned amounts contain (euros, TVA, frais de plateforme, taxe de séjour), though it says nothing about volume, sorting, or pagination behavior for a user-wide list.

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 tight sentences with zero filler: the first gives the action and filter scope, the second gives the return payload. Information is front-loaded and nothing repeats the title verbatim.

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 zero-required-parameter read tool with a fully described schema, the description supplies the one thing the schema cannot: what the response contains. Without an output schema this is nearly sufficient, with the only gap being ordering or result-size behavior that an agent might want to know.

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%, so the schema already documents the year, source, and property_id filters, including the enumeration of platform values. The description's parenthetical list of platforms and mention of 'bien, année, plateforme' restate the schema rather than adding format or edge-case meaning, so baseline 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?

States a specific verb and resource ('Liste les recettes locatives') plus the three optional filter axes, so the agent knows exactly what is returned. It does not name a sibling or explicitly distinguish itself from list_expenses or create_income, but the resource is unambiguous on its own.

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: 'avec filtres optionnels' tells the agent filters may be supplied but not when to supply them or when to prefer another tool. There are no exclusions or prerequisites, and no hint that a companion tool exists for creating or deleting incomes.

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