Skip to main content
Glama

Détail d'un avoir

get_credit_note
Read-onlyIdempotent

Détail d'une facture d'avoir : lignes reprises (quantités, remise en stock), montants, part déduite du reste à payer de la facture d'origine et part devenue avoir du client. (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_credit_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la facture d'avoir.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so '(Lecture seule.)' is largely redundant. What the description does add beyond structured data is the domain behavior of the record itself: which lines are restocked, and how the amount splits between a deduction from the original invoice balance and a credit balance for the customer.

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 lists the returned components compactly, with the resource named first. The trailing '(Lecture seule.)' is redundant against readOnlyHint and is the only wasted text.

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 single-parameter read getter with full schema coverage and no output schema, the description supplies exactly what is otherwise missing: the shape of the returned record. Only the absence of explicit sibling routing keeps it from being fully complete.

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 'id' parameter is already documented as the credit note identifier. The description adds no format, sourcing, or error semantics for the id, so the schema does all the work; 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 states a specific verb-resource pair ('Détail d'une facture d'avoir') and enumerates the content exposed: reprise lines with quantities and restocking, amounts, the portion deducted from the original invoice's remaining balance, and the portion converted into customer credit. It is clearly a single-record getter rather than a list, though it never names list_credit_notes as the alternative.

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 by 'Détail' plus the required id: fetch one credit note by identifier. There is no explicit when-to-use or when-not-to-use statement, and no pointer to list_credit_notes for browsing, so the agent must infer the boundary from the name.

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