Skip to main content
Glama

Tableau de bord

get_dashboard_stats
Read-onlyIdempotent

Résumé chiffré, mêmes chiffres que les cartes du tableau de bord : nb produits, clients, factures impayées, chiffre d'affaires du jour / de la semaine (lundi-dimanche) / du mois (caisse + factures, ventes annulées exclues), dépenses et revenu net du mois. (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_dashboard_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so '(Lecture seule.)' adds nothing and the bar is lower. Beyond that, the description does add real behavioral substance: the week is defined as Monday–Sunday, revenue includes both cash register and invoices, and cancelled sales are excluded — computation rules an agent cannot get from structured fields.

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 with the metric list front-loaded and the qualifiers (period definitions, exclusions) attached inline where they matter. The trailing '(Lecture seule.)' is redundant with annotations and could be dropped, but otherwise every clause carries information.

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 carries the full burden of describing return content, and it enumerates every metric plus the inclusion/exclusion rules — strong coverage. It does not state the response shape or field names, which is a minor residual gap for a tool this simple.

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?

The tool takes zero parameters, so the baseline of 4 applies and there is nothing for the description to compensate for. The description correctly spends no words on parameters.

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 enumerates exactly what the tool returns (product/customer counts, unpaid invoices, revenue for day/week/month, expenses, net income), which is a specific and unmistakable purpose. It stops short of naming which sibling to use instead (e.g. get_full_report, get_sales_report), so differentiation is by content rather than by explicit contrast.

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: it is the dashboard-card summary, so an agent can infer it is the quick overview call, and the zero-parameter signature reinforces that. There is no explicit when-to-use / when-not guidance and no pointer to the richer report siblings for deeper analysis.

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