Skip to main content
Glama

depenses

List expense invoices with linked client, quote, or invoice IDs; filter by client, project, category, or date range.

Instructions

Liste les dépenses (factures de frais). Chacune dit à quel client, devis ou facture elle est rattachée (client_id, devis_id, facture_id, numéros du compte). Filtrables par client (client_id = numéro du client dans le compte), par chantier (numéro du chantier, ancien regroupement), catégorie ou période (debut / fin en AAAA-MM-JJ, inclus).

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

Input Schema

NameRequiredDescriptionDefault
finNo
debutNo
dossierNo
categorieNo
client_idNo
chantier_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / client_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Client Id"
      +}
  2. Changed3 schema fields changedv0.2.1
    • addedInput schema / properties / debut
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Debut"
      +}
    • addedInput schema / properties / dossier
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Dossier"
      +}
    • addedInput schema / properties / fin
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Fin"
      +}
  3. First observedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It is reasonably clear this is a read/list operation and it discloses what each returned row contains (attachment to client, devis, or facture), which is valuable given there is no output schema. It omits pagination, volume, and authorization behavior, so the disclosure is only partial.

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 purpose is front-loaded in the first sentence, followed by structure and filter details. It is appropriately sized for six filters, with only mild parenthetical clutter.

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 six-parameter, no-annotation, no-output-schema tool this covers most of what an agent needs — purpose, filter semantics, and partial return content. However, the dossier parameter goes undocumented and there is no note on result size or ordering, leaving clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage the description must compensate, and it does for most parameters: client_id (client number in account), chantier (site number, legacy grouping), catégorie, and debut/fin (defined as AAAA-MM-JJ and inclusive). The dossier parameter is never mentioned, leaving one of six filters undocumented in both schema and description.

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?

States a specific verb and resource ('Liste les dépenses (factures de frais)') and clarifies the resource type, so it can be told apart from write-oriented siblings like ajouter_depense. It does not, however, name a specific sibling or contrast its scope, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description lists available filters but never says when to use this tool versus alternatives such as journal_achats, justificatifs_depense, or ajouter_depense. Usage is only implied by the list semantics, with no exclusions or prerequisites.

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