Skip to main content
Glama
benswel

QR for Agent

list_qr_codes

Browse and search existing QR codes with pagination to view short IDs, target URLs, labels, and timestamps.

Instructions

List all managed QR codes with pagination. Returns short IDs, target URLs, labels, and timestamps. Use this to browse or search for existing QR codes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return.
offsetNoNumber of results to skip.

Implementation Reference

  • The tool 'list_qr_codes' is defined here as part of the MCP tools configuration. The handler calls the underlying '/api/qr' endpoint with limit and offset parameters.
    list_qr_codes: {
      description:
        "List all managed QR codes with pagination. Returns short IDs, target URLs, labels, and timestamps. Use this to browse or search for existing QR codes.",
      inputSchema: z.object({
        limit: z.number().min(1).max(100).default(20).describe("Max results to return."),
        offset: z.number().min(0).default(0).describe("Number of results to skip."),
      }),
      handler: async (input: { limit: number; offset: number }) => {
        return apiRequest("/api/qr", { query: { limit: input.limit, offset: input.offset } });
      },
    },
Behavior3/5

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

With no annotations provided, description carries full burden. It successfully discloses pagination behavior and return structure (short IDs, target URLs, labels, timestamps). However, does not explicitly state this is read-only/safe or mention rate limits despite being a bulk list operation.

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 tightly constructed sentences with zero waste. Front-loaded with action ('List all managed QR codes'), followed by return value disclosure, then usage guidance. Every sentence earns its place.

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?

Appropriately complete for a low-complexity tool (2 params, simple pagination). Compensates for missing output schema by describing return values in text. Could improve by explicitly stating read-only nature and clarifying relationship to get_qr_code sibling.

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%, establishing baseline 3. Description adds contextual meaning by mentioning 'pagination' which clarifies the relationship between limit and offset parameters, though does not add syntax details beyond schema.

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?

Description states specific verb 'List' with resource 'managed QR codes' and mechanism 'pagination'. Clearly distinguishes from sibling create/update/delete operations and differentiates from get_qr_code (single fetch) by emphasizing 'all' and 'browse'.

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?

Provides clear usage context ('Use this to browse or search for existing QR codes') indicating when to use the tool. However, lacks explicit contrast with sibling get_qr_code (use for single QR details) or mention that parameters are optional for full listing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/benswel/qr-agent-core'

If you have feedback or need assistance with the MCP directory API, please join our Discord server