Skip to main content
Glama

qr: QR codes that never expire

List my QR codes

list_qr_codes
Read-only

List the codes of the account behind the API key, newest first, with scan counts. Needs an API key.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/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 usefully adds that results are ordered newest first, include scan counts, and are scoped to the API key's account — genuine value beyond the annotations. It stays silent on pagination behavior and whether a total count is returned, which matters given limit/offset exist.

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 front-loaded sentence with zero filler; the scope, ordering, and payload are delivered immediately, and the auth note follows compactly.

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 simple read-only list tool with annotations and no output schema, this covers scope, ordering, and returned fields adequately. However, it omits pagination semantics and any indication of result-set size or total count, which are the main unknowns an agent faces when calling it.

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 description carries the burden for the two pagination parameters, and it says nothing about them. The schema supplies defaults and bounds (limit max 100, offset default 0), but neither field's meaning nor page-size limits are explained anywhere, leaving an agent to guess at paging behavior.

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 ('List the codes') plus scope ('of the account behind the API key'), so an agent knows this is an account-wide enumeration, not a single-code lookup. It does not explicitly name how it differs from siblings like get_qr_code_stats, but the plural, account-scoped framing makes the distinction inferable.

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?

'Needs an API key' is an authentication prerequisite, not usage guidance. The description never says when to prefer this over get_qr_code_stats or create_qr_code, and gives no exclusions or conditions for use.

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.