Skip to main content
Glama

Caelara Labs Dynamic Media

qr_code_svg_builder

Encode text or a URL as a scannable QR code SVG

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": {
      "text": "<text>"
    },
    "name": "qr_code_svg_builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground color (hex, with or without #)
fgNoModule color (hex, with or without #)
eccNoError correction: L, M (default), Q or H
sizeNoRendered size in px (64-2048, default 256)
textYesText or URL to encode (max 1000 bytes)
formatNojson (default, includes svg + data URI) or svg (raw image/svg+xml)
marginNoQuiet zone in modules (0-16, default 4)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden. It discloses the output artifact (a scannable SVG) and implies validity, but says nothing about determinism, encoding constraints (the 1000-byte max lives only in the schema), or what the response looks like. It adds some context but leaves real behavioral questions unanswered.

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?

It is a single front-loaded sentence with no waste, stating the input types and output artifact directly. Nothing needs to be trimmed.

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?

For a stateless generation tool with all seven parameters documented in the schema and no output schema, the description is adequate but thin. It does not address output shape or the difference between the json and svg format modes, leaving the schema to carry that load.

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%: text, bg, fg, ecc, size, margin, and format are all documented in the schema with defaults and ranges. The description adds no additional parameter meaning beyond that, so the baseline of 3 applies.

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 uses a specific verb-plus-resource formulation, 'Encode text or a URL as a scannable QR code SVG', so the agent immediately knows it produces an SVG QR code. It does not explicitly name a sibling or boundary, but the purpose is distinct from the SVG generators like badge_shield_generator and avatar_initials_svg.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites, and no exclusions. The agent must infer from the tool name and description that this is the QR-generation path rather than a general SVG tool.

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