Skip to main content
Glama
Sign In

Snip

by link.snip
OverviewDiscussionsAdmin

Make a QR code

make_qr_code
Read-onlyIdempotent

Make a static QR code for a link, text, Wi-Fi network, contact card, email, phone number or SMS, free and with no account. Returns a PNG and an SVG download link that the user can open, save or print; show the PNG link to the user. Static codes hold the content in the pattern, so they never expire and keep working without Snip.link. Use this whenever the user asks for a QR code.

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": {
      "data": "<data>"
    },
    "name": "make_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground colour, #rrggbb. Default #ffffff.
fgNoDark colour, #rrggbb, for example #111111. Default #111111.
eccNoError correction: L 7%, M 15% (default), Q 25%, H 30% of the code can be damaged and still scan.
dataYesWhat the QR code holds: a web address, plain text, a WIFI:T:WPA;S:<name>;P:<password>;; string, a vCard, mailto:, tel: or sms:. For a link the user may want to change or track later, call shorten_link instead and use its QR code.
styleNoDot shape. Default rounded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds valuable context: static codes never expire and work without Snip.link, the tool is free with no account, and it returns a PNG plus an SVG download link with an instruction to show the PNG to the user. It does not mention rate limits or failure modes, but the added behavioral detail is strong.

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?

The description is a single dense but well-structured paragraph, front-loaded with what the tool does and followed by output behavior and usage guidance. Every sentence earns its place, though it is slightly long and could be split for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining returns and does so by specifying PNG and SVG download links and telling the agent to show the PNG to the user. Together with annotations covering safety and schema covering parameters, it is complete for an agent to invoke this tool correctly.

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 the schema already explains data, colors, error correction, and style in detail. The description reinforces the supported data formats and the shorten_link alternative, but does not substantially extend the parameter semantics beyond the schema. Baseline 3 is appropriate.

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 names a specific verb and resource ('Make a static QR code') and enumerates supported content types (link, text, Wi-Fi, contact card, email, phone, SMS). It clearly distinguishes static QR generation from link shortening, so an agent can tell it apart from sibling tools such as shorten_link.

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

Usage Guidelines5/5

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

It explicitly says 'Use this whenever the user asks for a QR code' and directs users who need a changeable/trackable link to shorten_link instead. Both the when-to-use and the alternative path are stated directly.

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

All Snip toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources