Skip to main content
Glama

Lister les transactions

dandori_list_transactions
Read-onlyIdempotent

Lister les transactions du budget, filtrables par mois, catégorie et type

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

Input Schema

NameRequiredDescriptionDefault
typeNoincome (revenus) ou expense (dépenses)
monthNoMois (YYYY-MM)
space_idNoID de l'espace (champ spaces de dandori_daily_summary) ; par défaut l'espace principal
category_idNoID de la catégorie (voir dandori_budget_dashboard)
to_completeNotrue : seulement les transactions sans montant, tous mois confondus

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?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds essentially nothing beyond that: no mention of result ordering, pagination/limits, whether all months are returned when month is omitted, or what happens with an unknown space_id.

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?

A single short sentence that is front-loaded with the verb and resource and closes with the filter axes; nothing is padded. It is efficient, though the extreme brevity borders on under-specification rather than concision.

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?

With five all-optional parameters and no output schema, the description does only the minimum: it never explains the default behavior (main space, all months) or the to_complete mode that bypasses the month filter. Because annotations and the schema carry the safety and parameter story, this is adequate but not 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 description coverage is 100%, so the baseline of 3 applies; every parameter including space_id and to_complete is already documented in the schema. The description restates only three of the five filter dimensions and adds no semantics the schema lacks.

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?

"Lister les transactions du budget" gives a specific verb and a specific resource, and the filter axes (mois, catégorie, type) sharpen the scope. It does not, however, distinguish itself from siblings such as dandori_add_transaction or dandori_budget_dashboard, so the agent must rely on the name alone to pick it.

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?

The mention of month/category/type filters implies the read-and-filter use case, which is enough for an agent to infer when this is the right call. There is no explicit when-not guidance and no named alternative for aggregate views (e.g. dandori_budget_dashboard), leaving the routing decision to inference.

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