QRStuff MCP Server

Get scans by region

get_scans_by_region

Read-onlyIdempotent

Use this when the user wants scans per state or region within one country (country code required). Read-only.

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": {
      "country": "<country>"
    },
    "name": "get_scans_by_region"
  }
}

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
`region`	No	Region filter.
`country`	Yes	ISO 3166-1 alpha-2 country code (required).
`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.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint, so 'Read-only' merely repeats structured data. Nothing is added about aggregation behavior, granularity of regional breakdown, or pagination beyond what the schema and output schema already provide.

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 with the usage trigger first and no filler. It is efficient, though its brevity is partly what leaves the gaps above.

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?

For a nine-parameter analytics tool with an output schema and full schema coverage, the description covers the calling condition and required input but omits how it differs from the country-level and location-based siblings. Adequate but with a clear routing gap.

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 description coverage is 100%, so all nine parameters, their defaults, enums, and conditional requirements (idproject/idqrcode) are already documented. The description only echoes that country is required, matching the schema's '(required)' note, adding no new meaning.

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 and resource with scope qualifier ('scans per state or region within one country'), which implicitly separates it from the sibling get_scans_by_country. It stops short of naming that sibling or clarifying the distinction explicitly.

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?

'Use this when the user wants scans per state or region within one country' gives a clear triggering condition and a required-input precondition. No exclusions or named alternatives (e.g., get_scans_by_country, get_top_performing_location) are offered.

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?