QR for Agent

create_text_qr

Create a QR code that encodes plain text for direct display when scanned. Ideal for sharing messages, notes, or any freeform content.

Instructions

Create a QR code that contains plain text. When scanned, the text is displayed directly. Useful for messages, notes, or any freeform content.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>"
    },
    "name": "create_text_qr"
  }
}

Input Schema

Name	Required	Description	Default
`content`	Yes	Plain text content to encode.
`label`	No	Label for this QR code.
`format`	No	Image format.	svg
`foreground_color`	No	Hex color for dots.
`background_color`	No	Hex color for background.
`dot_style`	No	Dot shape.
`corner_style`	No	Corner shape.
`logo_url`	No	Logo URL or data URI.
`frame_style`	No	Frame style around QR.
`frame_text`	No	CTA text on frame (max 30 chars).
`frame_color`	No	Frame background color.
`frame_text_color`	No	Frame text color.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 30, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only describes the creation action without disclosing any behavioral traits such as side effects, permissions, rate limits, or what the output is. The description is minimal.

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?

The description is two sentences, front-loaded with the core action, and every sentence serves a purpose. No unnecessary words.

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 12 parameters and no output schema, the description does not explain the return value or how to use the created QR code. The schema covers parameter details, but the description lacks completeness for a parameter-rich tool.

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%, with all parameters documented. Baseline is 3. The description adds no additional meaning beyond what the schema 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 it creates a QR code containing plain text, with the specific verb 'Create' and resource 'text QR code'. It distinguishes from sibling tools like create_email_qr or create_wifi_qr by specifying 'plain text' and 'freeform content'.

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 mentions it is 'useful for messages, notes, or any freeform content', providing some guidance on when to use it. However, it does not explicitly contrast with siblings like create_qr_code (which might be for URLs) or state when not to use it, leaving ambiguity.

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