media-gen-mcp

generate_qrcode

Generate QR codes as SVG or PNG from any text or URL with local rendering. No network or external tools required.

Instructions

Generate a QR code (二维码) as SVG or PNG from text/URL. Pure local rendering — no qrencode/zbar/system install, no AI, no network. Just call with the text/URL to encode. Multilingual triggers: QRコード · código QR · code QR · QR-Code · QR-код · código QR (ja/es/fr/de/ru/pt).

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": "generate_qrcode"
  }
}

Input Schema

Name	Required	Description	Default
`dark`	No	Foreground color, default #000000
`name`	No	Output filename (without extension)
`text`	Yes	Content to encode (URL or text)
`light`	No	Background color, default #ffffff
`format`	No		svg
`margin`	No	Margin in modules (default 2)
`outDir`	No	Output directory, default session-dir/output
`errorCorrectionLevel`	No		M

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.7Jul 14, 2026

TDQS

A4/5.0

Behavior3/5

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

Discloses local rendering, no system installs, no network. With no annotations, description carries transparency burden but omits details on limits, errors, or performance. Adequate but not comprehensive.

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?

Concise, well-structured description with front-loaded purpose. All sentences add value. No wasted words.

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?

Adequate for a 8-param tool with no output schema. Explains core functionality, self-contained nature, and multilingual triggers. Could mention output details but is largely complete.

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 coverage is 75%, so baseline is 3. Description adds minimal parameter info beyond schema; the main text mentions text/URL but doesn't elaborate on colors, margin, etc.

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?

Clearly states verb (Generate), resource (QR code), output formats (SVG/PNG), and source (text/URL). Distinguishes from sibling generate_* tools by specifying QR code specifically.

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?

Highlights pure local rendering with no dependencies, implying use when simplicity and offline capability are needed. Lacks explicit exclusion of alternatives but provides clear context.

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

Deploy Server