Skip to main content
Glama

qr: QR codes that never expire

QR code scan statistics

get_qr_code_stats
Read-only

Scans, daily unique visitors, scans per day, top cities and devices of a code. Anonymous and privacy-friendly (no IPs, no cookies).

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": {
      "code": "<code>"
    },
    "name": "get_qr_code_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe short code, e.g. "k7Fq2" (the part after ?c= in the short URL)
daysNo
edit_keyNoFor codes created without an API key: the edit_url (or its key) returned at creation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description contributes real behavioral context beyond them: the data collection is anonymous and privacy-friendly with no IPs or cookies, which tells the agent why there is no per-visitor identification and tempers expectations about geolocation precision. It omits any note on rate limits or how far back data is retained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with zero filler, front-loading the metrics and trailing the privacy note as secondary context. Nothing could be removed without losing information.

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?

With no output schema, the description usefully enumerates the return fields (scans, daily uniques, scans per day, cities, devices), which carries most of the burden. However, for a three-parameter tool it leaves open whether edit_key is required for codes created without an API key and never explains the days window, so an agent still has gaps before calling it correctly.

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 67%: `code` and `edit_key` are documented in the schema, but `days` (default 30, max 365) has no description anywhere, and the definition never clarifies that it sets the reporting window. The description spends its words on the returned metrics rather than adding meaning to any parameter, so it does not compensate for the coverage gap.

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 the concrete metrics returned (scans, daily unique visitors, top cities, devices) for a specific resource (a short code), which clearly separates it from create_qr_code, update_qr_code and list_qr_codes. It stops short of a clean verb+resource statement (it reads as a noun list) but an agent can still determine the purpose immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no statement about prerequisites (e.g., whether private codes need edit_key to read stats), and no routing language versus siblings such as list_qr_codes or get_limits. The use case is inferable only from the fact that the tool reports metrics.

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.