Skip to main content
Glama

Budget du mois

dandori_budget_dashboard
Read-onlyIdempotent

Résumé budget d'un mois dans un espace : solde, revenus, dépenses, catégories (avec leurs ID), alertes, dernières transactions, dépenses et revenus récurrents (recurring, avec leurs ID), et les espaces du compte (Perso, Pro…) avec leurs ID

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_budget_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoMois (YYYY-MM), par défaut le mois en cours
space_idNoID de l'espace (champ spaces de dandori_daily_summary) ; par défaut l'espace principal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description's real contribution is the returned payload contents, including that categories, recurring items, and spaces are returned with their IDs — useful for chaining into other calls. It adds no further details on volume, limits, or freshness beyond what annotations and schema provide.

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 dense sentence that is front-loaded with the core purpose ('Résumé budget d'un mois dans un espace') before enumerating contents. It is long but every clause names a distinct returned section; no filler wording.

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?

With no output schema, the description must disclose what comes back, and it does so comprehensively. Defaults and formats are handled by the fully covered schema, so the only remaining gap is guidance on when to choose this tool over alternatives.

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%: both month (YYYY-MM, defaults to current) and space_id (defaults to main space, references the spaces field of dandori_daily_summary) are already documented. The description only restates the space scoping ('dans un espace') and adds no format or resolution detail beyond the schema.

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 names a specific resource and scope — a monthly budget summary within one space — and enumerates the exact sections returned (balance, income, expenses, categories, alerts, recent transactions, recurring items, spaces). Combined with the title, an agent can distinguish this aggregate view from sibling mutation tools like dandori_add_transaction, though it never names an alternative dashboard 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: a 'résumé' of a month is what an agent would call for an overview. There is no statement of when to prefer this over other dashboards or transaction-level tools, and no prerequisites or exclusions are given.

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