Skip to main content
Glama
OpenLMNP

OpenLMNP

List Expenses

list_expenses
Read-only

Retrieve deductible LMNP expenses and filter them by property, fiscal year, or category to support French tax reporting.

Instructions

Liste les charges déductibles de l'utilisateur avec filtres optionnels par bien, année et catégorie. Catégories disponibles : property_tax, insurance, energy, maintenance, supplies, platform_fees, accounting, telecom, travel, cleaning, other.

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

Input Schema

NameRequiredDescriptionDefault
yearNoFiltrer par année fiscale, ex: 2024 (optionnel)
categoryNoFiltrer par catégorie : property_tax, insurance, energy, maintenance, supplies, platform_fees, accounting, telecom, travel, cleaning, 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 / category / description
      Added value: +"Filtrer par catégorie : property_tax, insurance, energy, maintenance, supplies, platform_fees, accounting, telecom, travel, cleaning, other (optionnel)"
    • addedInput schema / properties / property_id / description
      Added value: +"Filtrer par identifiant de bien (optionnel)"
    • addedInput schema / properties / year / description
      Added value: +"Filtrer par année fiscale, ex: 2024 (optionnel)"
  2. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe, non-mutating read, so the bar is lower. The description adds that the scope is the calling user's deductible expenses, which is useful beyond the annotations, but it says nothing about default behavior (all years vs. current), result ordering, or pagination limits.

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?

Two front-loaded sentences that identify the resource first and the filters second. The category enumeration duplicates the schema's category list almost verbatim, which is mildly redundant, but it is short enough not to be wasteful.

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 read-only list tool with three optional, fully documented parameters and no output schema, the description covers the essential scope and filtering surface. What is missing (default time range, whether results are paginated) is minor, though the French-only description is a mild inconsistency with an otherwise English toolset.

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 each of the three parameters is already documented in the schema, including examples and the category enumeration. The description restates the same three filter axes and the same category list without adding format, default, or combination semantics, 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?

The description names a specific verb and resource ('Liste les charges déductibles de l'utilisateur') and states the supported filter axes, so an agent knows it is a plural listing of deductible expenses. It does not explicitly distinguish itself from siblings like get_expense (single record) or create_expense, leaving that differentiation to the agent's inference from the name.

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?

It states that the filters are optional (property, year, category), which implies calling with no arguments returns the user's full expense set. However, there is no explicit when-to-use guidance, no mention of when to prefer get_expense for a single record, and no prerequisites or exclusions stated.

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