QRStuff MCP Server

Get scans by country

get_scans_by_country

Read-onlyIdempotent

Use this when the user wants scans per country. Read-only.

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

Input Schema

Name	Required	Description	Default
`page`	No	Page number.
`scope`	No	account for everything, project for one project (needs idproject), qrcode for one code (needs idqrcode and its idproject).	account
`end_date`	No	End of the period, YYYY-MM-DD. Leave empty for today. Always send it when the user names a period.
`idqrcode`	No	QR code ID from `list_qrcodes`. Required when scope is qrcode. Never guess an ID.
`per_page`	No	Items per page.
`idproject`	No	Project ID from `list_projects`. Required when scope is project or qrcode. Never guess an ID.
`start_date`	No	Start of the period, YYYY-MM-DD. Leave empty for the last 30 days. Always send it when the user names a period.

Output Schema

Name	Required	Description	Default
`total`	No
`buckets`	No
`per_page`	No
`last_page`	No
`current_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 30, 2026

changedInput schema / properties / end_date / description

Previous value: -"End date YYYY-MM-DD. REQUIRED when the user asks for a specific period; do not omit if they mention dates. Defaults to today only when no range given."New value: +"End of the period, YYYY-MM-DD. Leave empty for today. Always send it when the user names a period."

changedInput schema / properties / idproject / description

Previous value: -"Project ID. Required when scope=project or qrcode."New value: +"Project ID from `list_projects`. Required when scope is project or qrcode. Never guess an ID."

changedInput schema / properties / idqrcode / description

Previous value: -"QR code ID. Required when scope=qrcode."New value: +"QR code ID from `list_qrcodes`. Required when scope is qrcode. Never guess an ID."

changedInput schema / properties / scope / description

Previous value: -"Scope: account (default), project, or qrcode"New value: +"account for everything, project for one project (needs idproject), qrcode for one code (needs idqrcode and its idproject)."

changedInput schema / properties / start_date / description

Previous value: -"Start date YYYY-MM-DD. REQUIRED when the user asks for a specific period; do not omit if they mention dates. Defaults to 30 days ago only when no range given."New value: +"Start of the period, YYYY-MM-DD. Leave empty for the last 30 days. Always send it when the user names a period."

First observedOct 12, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description's only behavioral statement is 'Read-only' – a verbatim restatement of the annotation. It adds no context on scope resolution, defaults, or result shape beyond what the structured fields already give.

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, front-loaded sentences with no padding, but the second sentence ('Read-only') duplicates an annotation and so does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 7-parameter tool with a hierarchical scope model (account/project/qrcode) and optional date window gets a single sentence; the description never touches the scoping rules or date-range behavior. An output schema exists so return values need not be explained, but the invocation-relevant context is missing.

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 100% and the parameter descriptions already explain the scope enum, the idproject/idqrcode dependencies and date defaults in detail. The description adds nothing about parameters, so the baseline 3 applies.

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: returns scans aggregated per country. That is unambiguous in isolation, but the description never distinguishes this from the very similar sibling get_scans_by_region, which an agent could easily pick by mistake.

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?

'Use this when the user wants scans per country' gives a positive trigger, but there are no exclusions or named alternatives, so the country-vs-region choice against get_scans_by_region is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All QRStuff MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?