Skip to main content
Glama
OpenLMNP

OpenLMNP

Get Expense

get_expense
Read-only

Retrieve full expense details by ID, including tax-inclusive/exclusive amounts, VAT, category, recurrence, dedicated flag, and prorated effective amount for accurate LMNP accounting.

Instructions

Retourne le détail complet d'une charge par son identifiant : montant TTC/HT, TVA, catégorie, type de récurrence, flag dédié et montant effectif après application de la quote-part si non dédié.

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": {
      "expense_id": "<expense_id>"
    },
    "name": "get_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
expense_idYesIdentifiant de la charge

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / expense_id / description
      Added value: +"Identifiant de la charge"
  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?

With only readOnlyHint=true supplied and no output schema, the description carries useful behavioral weight by enumerating the returned fields (TTC/HT amounts, TVA, category, recurrence type, dedicated flag, and the effective amount after quote-part). That tells an agent what it gets back and clarifies that the 'dedicated' flag changes the meaning of the effective amount. It says nothing about error/not-found behavior or permissions.

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?

A single front-loaded sentence stating the operation first, then the returned content. The field enumeration earns its place precisely because no output schema exists, and there is no redundant or filler wording.

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 safety covered by annotations, the description is nearly sufficient: it explains the return content in detail. The only real gaps are failure behavior for a nonexistent ID and any explanation of domain terms like 'flag dédié' and 'quote-part' for a caller unfamiliar with the domain.

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 coverage is 100% and the single parameter is already documented as "Identifiant de la charge"; the description repeats that it is a lookup by identifier without adding format, type, or provenance guidance. Baseline 3 applies since the schema does the heavy lifting.

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 ("Retourne le détail complet d'une charge") plus the lookup key ("par son identifiant"), which clearly separates it from write siblings like create_expense or update_expense. It stops short of naming a sibling it is not (e.g., a list/search tool), so it is clear but not fully differentiated.

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: the phrase "par son identifiant" signals that the caller must already know or obtain an expense ID, hinting at a prior listing step. There is no explicit when-to-use statement, no exclusion (e.g., use get_dashboard_summary for aggregates), and no note on what happens for an unknown ID.

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