Skip to main content
Glama

QRavate QR codes

Exporter en CSV

export_qr_codes
Read-onlyIdempotent

Export CSV des QR codes, destinations et scans sur une période (plans Pro et Max).

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, non-destructive read, so the safety profile is covered. The description adds the plan gating and the data scope (QR codes, destinations, scans) beyond the annotations, but says nothing about export size limits, how the period is interpreted, or how the file/result is delivered.

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 front-loaded sentence that leads with the output format and scope, with no filler. It is perhaps too terse for a two-parameter, undocumented-schema tool, but nothing is wasted.

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?

Because there is no output schema, the description carries the job of explaining the return value, and it does state CSV with three data categories. It is still incomplete regarding omitted-parameter behavior and export constraints, which matter for a period-based export with two partially documented parameters.

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 burden is entirely on the description, which only says 'sur une période' — implying the two date parameters bound the range. It does not clarify that both are optional (required: 0), what default period applies when omitted, or whether endpoints are inclusive, leaving the agent to guess.

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 verb+resource combination ('Export CSV des QR codes, destinations et scans') and scopes it to a date period, so the agent knows exactly what comes out. It stops short of naming a sibling such as get_stats or compare_stats to distinguish when raw export is preferred over aggregated stats.

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 plan restriction ('plans Pro et Max') is a genuine usage prerequisite that tells the agent when this call will succeed. However, there is no guidance on when to choose this export over the sibling stats tools, and no statement about what happens when no period is supplied.

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