Skip to main content
Glama

QRavate QR codes

Comparer des QR codes

compare_stats
Read-onlyIdempotent

Compare les scans de plusieurs QR codes sur une période (par exemple un code par point de vente), avec un graphique des courbes superposées. Statistiques avancées : plans Pro et Max.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "qrs": "<qrs>"
    },
    "name": "compare_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
qrsYes
fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two useful behavioral facts beyond them: the result is rendered as a multi-curve chart and the tool is gated to Pro/Max plans. It omits what happens if no period is supplied and how many codes may be compared (the 50 cap lives only in the schema).

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?

Two short sentences, front-loaded with the core action and output, with the plan restriction placed last. Nothing is redundant, though the parenthetical example and the plan note could be tightened slightly.

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?

For a read-only comparison tool with no output schema, the definition covers the action, the visual output, a use case and the plan gate. The main remaining gap is date-range defaults/format, but annotations and schema cover the remainder adequately.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the meaning of the three parameters. It only conveys that the comparison spans 'une période' and that each array entry is typically 'un code par point de vente'; it never clarifies that 'from'/'to' are YYYY-MM-DD bounds, whether they are optional with defaults, or that 'qrs' takes 2-50 identifiers.

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?

Specific verb + resource: 'Compare les scans de plusieurs QR codes sur une période' plus the output form (graphique des courbes superposées). This distinguishes it implicitly from single-code stat tools like get_stats by stating it works across several codes. It does not name a sibling explicitly, so it stops short of 5.

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?

Provides a concrete usage scenario ('par exemple un code par point de vente') and a plan prerequisite ('plans Pro et Max'), which is real guidance. However it never says when to prefer this over get_stats or export_qr_codes, nor any exclusion such as the minimum of 2 codes enforced by the schema.

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