QRStuff MCP Server

Get unique users

get_unique_users

Read-onlyIdempotent

Use this when the user asks how many different people scanned, not how many scans. Same scopes and dates as get_total_scans. 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_unique_users"
  }
}

Input Schema

Name	Required	Description	Default
`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.
`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
`growth`	No
`unique_users`	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

A4.4/5.0

Behavior4/5

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

Annotations already carry readOnlyHint, idempotentHint and destructiveHint=false, so 'Read-only' in the description is redundant. The valuable addition is 'Same scopes and dates as `get_total_scans`', which tells the agent the parameter contract is shared with a known sibling. It does not describe the return shape, but an output schema exists.

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?

Three short sentences with the disambiguating condition front-loaded and zero filler; every sentence contributes routing or contract information.

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?

With rich annotations, a complete schema and an output schema covering return values, the description needs only purpose and disambiguation, which it supplies. A note on how uniqueness is computed (e.g. by device vs IP) would have made it fully complete.

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 every parameter is already documented in the schema, including scope semantics and the 'never guess an ID' guidance. The description adds no parameter detail of its own beyond cross-referencing get_total_scans, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource and the exact question it answers ('how many different people scanned') and contrasts it directly with counting scans, which pins it against sibling get_total_scans.

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

Usage Guidelines5/5

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

Gives an explicit trigger condition ('when the user asks how many different people scanned, not how many scans') and names the alternative tool implicitly, so the agent knows exactly when to pick this one over get_total_scans.

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?