Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_media_qr_code_svg_builder

Encodes text or a URL into a scannable QR code SVG with configurable size, colors, margin and error correction, returning raw SVG or JSON with a data URI.

Instructions

[Dynamic Media] Encode text or a URL as a scannable QR code SVG Measured p50 12 ms, p95 42 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://media.caelaralabs.com.

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": "caelara_media_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 observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the burden, and it does disclose two useful behavioral facts: measured latency (p50 12 ms, p95 42 ms) and that the tool calls an external service at https://media.caelaralabs.com, implying a network dependency. It says nothing about authentication, rate limits, failure modes, or whether the operation has side effects — so a mutation-free read/generate profile must be assumed rather than stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the purpose, with zero filler or repetition. The benchmark stamp and endpoint URL are dense but arguably earn their place as provenance and dependency signals.

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 7-parameter generator with no output schema, the description should say what comes back (raw SVG vs. JSON containing svg plus data URI) and note any constraints on the external call. The format parameter's schema text covers the output shape indirectly, so this is adequate but not self-sufficient.

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 every one of the 7 parameters (bg, fg, ecc, size, text, format, margin) is already documented with ranges and defaults in the schema. The description only restates that text or a URL is encoded, adding no new meaning beyond the schema; baseline 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?

"Encode text or a URL as a scannable QR code SVG" gives a specific verb (encode), resource (text/URL), and concrete artifact (QR code SVG). It is easy to distinguish from the SVG-producing siblings (avatar initials, badge shield, OG card) since none of them produce QR codes, but the description never explicitly contrasts itself with them.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no mention of any alternative tool. The only implicit signal is the "[Dynamic Media]" category tag and the SVG output format.

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

Deploy Server

Other Tools