Skip to main content
Glama

SiteCheck

by io.github.bck-stack
OverviewDiscussionsAdmin

Qr

qr
Read-only

A QR code for a text of up to 300 characters (a URL, Wi-Fi login or contact card), generated locally. format=svg returns the image itself as image/svg+xml; format=json returns the version, the module count, the SVG and a data URI. Error correction L, M, Q or H (default M); size from 128 to 1024 pixels (default 512). Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Input Schema

NameRequiredDescriptionDefault
eccNoL, M, Q or H (default M)
sizeNoPixels, 128 to 1024 (default 512)
textYesUp to 300 characters
formatNosvg (default) or json

Output Schema

NameRequiredDescriptionDefault
eccNo
svgNo
textNo
dataUriNo
modulesNo
versionNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "checkedAt": {},
+    "dataUri": {},
+    "ecc": {},
+    "modules": {},
+    "svg": {},
+    "text": {},
+    "version": {}
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses local generation, exact format-dependent outputs, error correction levels, size range, pricing of $0.002 USDC per successful call via x402, supported payment networks, and that failed calls are not charged. This is unusually rich behavioral context for an agent deciding whether and how to call the tool.

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 front-loaded with the core purpose and then efficiently covers formats, error correction, size, and pricing. Every sentence adds information relevant to calling the tool correctly.

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?

Although an output schema exists, the description still provides enough about format-dependent returns, local generation, payment behavior, and failure charging to make the tool fully understandable. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters and defaults. The description adds useful meaning beyond the schema by giving concrete text examples and explaining what format=svg versus format=json returns, including version, module count, SVG, and data URI.

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 states a specific verb and resource: it generates a QR code for text such as a URL, Wi-Fi login, or contact card. It immediately distinguishes this from sibling utilities like image or encode by naming the exact output and input domain.

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?

Usage is implied by the clear purpose, and the description explains format choices and constraints, but it does not explicitly say when to use this tool versus alternatives or when not to use it. With no direct QR sibling, the guidance is adequate but not explicit.

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

All SiteCheck 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