Skip to main content
Glama

QR redirects, recipient codes and scans

spur_get_qr_manager
Read-onlyIdempotent

Read standalone redirects, recipients, manager activity, scan events, or dated analytics, including codes not attached to postcards. List results retain server pagination.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral facts beyond that: results are server-paginated and postcard-unattached codes are included. It says nothing about permission requirements, rate limits, or empty-result behavior, so the addition is real but modest.

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 sentences, front-loaded with the enumerated sections and the standalone-code scope before the pagination note; no filler. The comma-separated list is dense but each item corresponds to a real section value, so nothing is wasted.

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?

This is a polymorphic tool with six distinct section modes and no output schema, and the description covers every mode plus pagination behavior. The remaining gap is mode-specific prerequisites (which sections require redirect_id and that analytics needs start/end), which an agent would otherwise only discover by reading the oneOf branches.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description goes further by mapping the polymorphic 'section' discriminator onto concrete capabilities (redirects, recipients, manager, scans, analytics), which helps an agent pick the correct oneOf branch. It does not explain that redirect_id is required for the non-'redirects' sections or what start/end date boundaries mean.

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 a specific read operation and enumerates the resources returned: redirects, recipients, manager activity, scan events, and dated analytics. The clause 'including codes not attached to postcards' scopes it away from postcard-attached QR data, giving partial sibling differentiation, though it never names a specific alternative tool.

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?

Usage is implied rather than stated: an agent can infer this is the read path for standalone QR data and that 'codes not attached to postcards' is the differentiator, but there is no explicit 'use this instead of X' or 'do not use for Y' guidance against siblings like spur_list_qr_codes, spur_get_qr_code_activity, or spur_manage_qr_recipients.

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.

Resources