Skip to main content
Glama

Détail d'une dépense

get_expense
Read-onlyIdempotent

Détails d'une dépense par ID. (Lecture seule.)

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

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la dépense.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and '(Lecture seule.)' merely restates that. Nothing is added about behavior on a missing/unauthorized ID, error shape, or what the returned detail contains, so beyond the structured fields the description contributes almost nothing.

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 short fragments with the key information (resource + lookup key) front-loaded and zero padding. It is arguably under-written rather than verbose, so brevity is not the issue.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-ID read whose safety profile and parameter are fully covered by annotations and schema, the essentials are present. However, with no output schema, a brief note on what the returned expense detail includes would have closed the remaining gap.

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 parameter and 100% schema description coverage, the schema already fully documents 'id' as the expense identifier. The phrase 'par ID' only echoes the schema, which is the expected baseline for full coverage.

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?

'Détails d'une dépense par ID' states a specific verb (retrieve details) and resource (expense) plus the lookup key. It is clearly distinguishable from list_expenses, though it does not name or contrast 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 expense when you have its ID. There is no explicit statement of when to prefer this over list_expenses or of what happens with an unknown ID, so the agent must infer the context.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources