Skip to main content
Glama

QRavate QR codes

Statistiques de scans

get_stats
Read-onlyIdempotent

Statistiques de scans pour un QR ou tout l’espace, à utiliser pour toute question sur les scans ou les performances des QR codes ; le résultat s’affiche en tableau de bord graphique. Par jour, pays et type d’appareil sur tous les plans ; villes, systèmes, navigateurs, langues, heures, jours de la semaine et évolution avec les statistiques avancées (Pro et Max). Dates AAAA-MM-JJ, heure de Paris ; 30 derniers jours par défaut.

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

Input Schema

NameRequiredDescriptionDefault
qrNo
toNo
fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior, so the bar is lower. The description still adds substantive context: the output is a graphical dashboard rather than raw data, metric availability is gated by plan (Pro/Max for cities, systems, browsers, languages, hours, weekdays, trends), and the default window is the last 30 days in Paris time.

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 and the recommended use case are front-loaded, and every clause adds information (metrics, plan tiers, date format, default window). It is dense and semicolon-chained, which makes it slightly harder to scan than it could be, but nothing is redundant.

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?

There is no output schema, so the description appropriately explains what comes back (a dashboard) and which dimensions can be broken out. Combined with plan-gating notes and date semantics, an agent has enough to call it correctly; only the exhaustive metric list per plan tier is left implicit.

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?

Schema coverage is 0%, so the description must carry the load, and it does explain the date format (AAAA-MM-JJ), the timezone (Paris), and the default range (30 last days). It also implies that omitting the qr parameter yields whole-workspace stats. Minor gap: it never explicitly states that from/to are inclusive bounds or which of the two dates is the start.

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+resource: scan statistics for a single QR code or the whole workspace, rendered as a graphical dashboard. Scope (single QR vs. entire space) is explicit, but it never mentions the sibling compare_stats, so the agent must guess which of the two statistical tools to pick.

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?

Gives clear when-to-use guidance: 'à utiliser pour toute question sur les scans ou les performances des QR codes'. It also flags that advanced breakdowns require a Pro/Max plan, which is real decision-relevant context. It stops short of naming alternatives or exclusions.

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