Skip to main content
Glama

Factures en retard

get_overdue_invoices
Read-onlyIdempotent

Factures en retard de paiement (statut sent + due_date dépassée). Aucun outil de ce serveur ne change le statut d'un document (marquer une facture payée, l'émettre, l'envoyer, l'annuler) ni n'enregistre de paiement : ces actions se font seulement dans SAMA Entreprise, par un utilisateur autorisé. (Lecture seule.)

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": "get_overdue_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximum de factures renvoyées (défaut 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, and the description is consistent with them while adding the server-wide capability boundary and the exact status/date condition that defines 'overdue'. It does not mention result ordering, timezone handling for due_date, or whether partially paid invoices count, which would be useful behavioral detail.

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?

The qualifying condition is front-loaded in the first sentence, followed by the capability caveat, which is the right order. The trailing '(Lecture seule.)' largely repeats readOnlyHint and is mild redundancy, but the text is otherwise tight.

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 tool with rich annotations, the definition covers the filter semantics and the server's write limitations. With no output schema, it could say a bit more about what each returned invoice contains or how results are ordered, but nothing critical to calling it correctly is missing.

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% for the single 'limit' parameter, including its default of 20, so the schema already carries the meaning. The description adds nothing about the limit or about ordering/truncation of results, 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 gives a precise predicate for the resource: invoices whose status is 'sent' and whose due_date has passed. That is far more specific than the title 'Factures en retard' and lets an agent distinguish it from a general invoice lister. It stops short of naming the sibling to use for all invoices, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It sets a clear usage boundary by stating that no tool on this server can change a document's status (mark paid, issue, send, cancel) or record a payment, and that those actions happen only in SAMA Entreprise by an authorized user. That prevents the agent from hunting for a write path. It does not say when to prefer this over list_invoices with a status filter, which is the remaining gap.

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