Skip to main content
Glama
benswel

QR for Agent

create_event_qr

Generate QR codes that add calendar events when scanned. Encodes iCalendar VEVENT data for easy import into calendar applications.

Instructions

Create a QR code that adds a calendar event when scanned. Encodes a standard iCalendar VEVENT that calendar apps can import.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesEvent title/summary.
startYesEvent start date-time in ISO 8601 format (e.g. 2026-03-15T09:00:00Z).
endYesEvent end date-time in ISO 8601 format.
locationNoEvent location.
descriptionNoEvent description.
labelNoLabel for this QR code.
formatNoImage format.svg
foreground_colorNoHex color for dots.
background_colorNoHex color for background.
dot_styleNoDot shape.
corner_styleNoCorner shape.
logo_urlNoLogo URL or data URI.
frame_styleNoFrame style around QR.
frame_textNoCTA text on frame (max 30 chars).
frame_colorNoFrame background color.
frame_text_colorNoFrame text color.

Implementation Reference

  • The handler for create_event_qr which constructs a POST request to /api/qr with event details.
    handler: async (input: Record<string, unknown>) => {
      const { summary, start, end, location, description, ...rest } = input;
      return apiRequest("/api/qr", {
        method: "POST",
        body: { type: "event", event_data: { summary, start, end, location, description }, ...rest },
      });
    },
  • Input schema validation for the create_event_qr tool.
    inputSchema: z.object({
      summary: z.string().describe("Event title/summary."),
      start: z.string().describe("Event start date-time in ISO 8601 format (e.g. 2026-03-15T09:00:00Z)."),
      end: z.string().describe("Event end date-time in ISO 8601 format."),
      location: z.string().optional().describe("Event location."),
      description: z.string().optional().describe("Event description."),
      label: z.string().optional().describe("Label for this QR code."),
      format: z.enum(["svg", "png"]).default("svg").describe("Image format."),
      foreground_color: z.string().regex(/^#[0-9A-Fa-f]{6}$/).optional().describe("Hex color for dots."),
      background_color: z.string().regex(/^#[0-9A-Fa-f]{6}$/).optional().describe("Hex color for background."),
      dot_style: z.enum(["square", "rounded", "dots", "classy-rounded"]).optional().describe("Dot shape."),
      corner_style: z.enum(["square", "extra-rounded", "dot"]).optional().describe("Corner shape."),
      logo_url: z.string().optional().describe("Logo URL or data URI."),
      frame_style: z.enum(["none", "banner_bottom", "banner_top", "rounded"]).optional().describe("Frame style around QR."),
      frame_text: z.string().max(30).optional().describe("CTA text on frame (max 30 chars)."),
      frame_color: z.string().regex(/^#[0-9A-Fa-f]{6}$/).optional().describe("Frame background color."),
      frame_text_color: z.string().regex(/^#[0-9A-Fa-f]{6}$/).optional().describe("Frame text color."),
    }),
  • The registration of create_event_qr in the tools object.
    create_event_qr: {
Behavior3/5

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

With no annotations provided, the description carries full burden. It adds valuable context about the iCalendar encoding standard, but misses critical behavioral details: what the tool returns (image data, URL, ID?), whether the QR is persisted to an account, permission requirements, or rate limits.

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 with zero waste. First sentence establishes the user-facing function (QR → calendar event), second sentence provides technical implementation detail (iCalendar VEVENT standard). Every word earns its place.

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?

With 16 parameters and 100% schema coverage, the input side is well handled. However, lacking both output schema and annotations, the description fails to specify what the tool returns (binary image, URL, object ID?) or persistence behavior, which are critical gaps for a creation tool.

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 coverage is 100%, establishing a baseline of 3. The description adds meaningful semantic context by stating the QR encodes 'iCalendar VEVENT', which clarifies how parameters like summary, start, end, and location map to calendar event fields rather than generic QR content.

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 explicitly states the tool creates a QR code that adds calendar events when scanned, specifying the iCalendar VEVENT standard. This clearly distinguishes it from sibling tools like create_email_qr, create_phone_qr, and create_wifi_qr by specifying the exact QR subtype and encoding format.

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?

While the description doesn't explicitly name alternatives, it provides clear context for selection by specifying 'calendar event' and 'iCalendar VEVENT'. This allows an agent to distinguish this tool from the 10+ other QR creation siblings for different purposes (email, SMS, WiFi, etc.).

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