Skip to main content
Glama
benswel

QR for Agent

by benswel
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

update_app_store_qr

Modify App Store QR code URLs for iOS, Android, or fallback destinations. Update labels and merge changes with existing data without regenerating the QR image.

Instructions

Update the app store URLs of an App Store QR code. Partial updates merge with existing data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
short_idYesThe short ID of the App Store QR code to update.
ios_urlNoApple App Store URL.
android_urlNoGoogle Play Store URL.
fallback_urlNoFallback URL.
labelNoUpdate the label.

Implementation Reference

  • packages/mcp/src/tools.ts:651-656 (handler)
    Handler for updating app store QR codes.
    handler: async (input: Record<string, unknown>) => {
  const { short_id, label, ...appStoreFields } = input;
  const body: Record<string, unknown> = { app_store_data: appStoreFields };
  if (label !== undefined) body.label = label;
  return apiRequest(`/api/qr/${short_id}`, { method: "PATCH", body });
},
  • packages/mcp/src/tools.ts:644-650 (schema)
    Input schema definition for update_app_store_qr.
    inputSchema: z.object({
  short_id: z.string().describe("The short ID of the App Store QR code to update."),
  ios_url: z.string().optional().describe("Apple App Store URL."),
  android_url: z.string().optional().describe("Google Play Store URL."),
  fallback_url: z.string().optional().describe("Fallback URL."),
  label: z.string().optional().describe("Update the label."),
}),
  • packages/mcp/src/tools.ts:641-657 (registration)
    Tool definition and registration for update_app_store_qr.
    update_app_store_qr: {
  description:
    "Update the app store URLs of an App Store QR code. Partial updates merge with existing data.",
  inputSchema: z.object({
    short_id: z.string().describe("The short ID of the App Store QR code to update."),
    ios_url: z.string().optional().describe("Apple App Store URL."),
    android_url: z.string().optional().describe("Google Play Store URL."),
    fallback_url: z.string().optional().describe("Fallback URL."),
    label: z.string().optional().describe("Update the label."),
  }),
  handler: async (input: Record<string, unknown>) => {
    const { short_id, label, ...appStoreFields } = input;
    const body: Record<string, unknown> = { app_store_data: appStoreFields };
    if (label !== undefined) body.label = label;
    return apiRequest(`/api/qr/${short_id}`, { method: "PATCH", body });
  },
},

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully discloses the merge semantics ('Partial updates merge with existing data'), but omits other critical behavioral details like error handling for non-existent short_ids, authentication requirements, or rate limiting.

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?

Two sentences total with zero waste: the first establishes purpose immediately, and the second provides essential behavioral context about merge semantics. Every word 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?

Given the high schema coverage and lack of output schema, the description is reasonably complete for an update operation. It covers the critical merge behavior, though it could benefit from mentioning success indicators or error scenarios since no output schema exists to document returns.

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 the baseline is 3. The description mentions 'app store URLs' conceptually grouping ios_url, android_url, and fallback_url, but does not add syntax details, format constraints, or examples beyond what the schema already provides.

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?

The description clearly states the specific action ('Update'), the target resource ('App Store QR code'), and distinguishes from siblings like update_social_qr or update_wifi_qr by specifying 'App Store' in the resource name.

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?

The description explains the partial update behavior ('merge with existing data'), which hints at usage patterns, but lacks explicit guidance on when to use this single-update tool versus bulk_update_qr_codes or when to prefer it over recreating the QR code.

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