Blackwood State

QR code

blackwood_qrcode_generate

Read-onlyIdempotent

Use when you need a qr code generator for a URL, text, Wi-Fi or payment link as an SVG image. Do not use for reading or decoding an existing QR code, logos, colored codes or PNG output. Returns JSON with a QR code for your text or URL as SVG markup and an SVG data URL, with error correction level and border options, generated by the uqr library for 0.004 USDC per call. Typical response time 500 ms (p95). Category: Media.

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

Input Schema

Name	Required	Description
`ecc`	No	Error correction level: L 7%, M 15% (default), Q 25%, H 30%
`text`	Yes	Text or URL to encode, e.g. https://example.com (up to 2000 characters)
`border`	No	Quiet zone around the code, in modules (default 2)
`pixelSize`	No	SVG units per module (default 10)
`response_format`	No	concise (the default when omitted) keeps the JSON short: long fields such as base64 images or audio come back as separate image/audio content blocks and other long strings are cut with a marker; detailed returns the full JSON

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "bytes": {
-        "type": "number"
-      },
-      "dataUrl": {
-        "type": "string"
-      },
-      "ecc": {
-        "type": "string"
-      },
-      "modules": {
-        "type": "number"
-      },
-      "svg": {
-        "type": "string"
-      },
-      "version": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "svg",
-      "dataUrl",
-      "version",
-      "modules",
-      "ecc",
-      "bytes"
-    ],
-    "type": "object"
-  },
-  {
-    "description": "x402 PaymentRequired (returned with isError when payment is needed)",
-    "properties": {
-      "accepts": {
-        "items": {
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "error": {
-        "type": "string"
-      },
-      "extensions": {
-        "type": "object"
-      },
-      "resource": {
-        "type": "object"
-      },
-      "x402Version": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "x402Version",
-      "accepts"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "bytes": {
+        "type": "number"
+      },
+      "dataUrl": {
+        "type": "string"
+      },
+      "ecc": {
+        "type": "string"
+      },
+      "modules": {
+        "type": "number"
+      },
+      "next": {
+        "additionalProperties": false,
+        "description": "Suggested next paid call in the same family (call it in a loop when the task continues)",
+        "properties": {
+          "method": {
+            "enum": [
+              "GET",
+              "POST"
+            ],
+            "type": "string"
+          },
+          "sample": {
+            "description": "Free fixed sample of the whole family",
+            "type": "string"
+          },
+          "service": {
+            "description": "Service id of the suggested next paid call",
+            "type": "string"
+          },
+          "tool": {
+            "description": "MCP tool name of the same call",
+            "type": "string"
+          },
+          "url": {
+            "description": "Paid route of the next call",
+            "type": "string"
+          },
+          "useWhen": {
+            "description": "When the next call is the right one",
+            "type": "string"
+          }
+        },
+        "required": [
+          "service",
+          "tool",
+          "method",
+          "url",
+          "useWhen",
+          "sample"
+        ],
+        "type": "object"
+      },
+      "svg": {
+        "type": "string"
+      },
+      "version": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "svg",
+      "dataUrl",
+      "version",
+      "modules",
+      "ecc",
+      "bytes"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "x402 PaymentRequired (returned with isError when payment is needed)",
+    "properties": {
+      "accepts": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "error": {
+        "type": "string"
+      },
+      "extensions": {
+        "type": "object"
+      },
+      "resource": {
+        "type": "object"
+      },
+      "x402Version": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "x402Version",
+      "accepts"
+    ],
+    "type": "object"
+  }
+]

AddedOct 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description goes well beyond that by disclosing cost (0.004 USDC per call), latency (500 ms p95), the rendering library (uqr), and the exact return shape (SVG markup plus an SVG data URL). These are operationally relevant traits an agent cannot get from the annotations.

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?

Front-loaded with the usage trigger and exclusions, then the return/behavioral facts, so an agent can stop reading early. Slightly dense and the trailing 'Category: Media' is redundant metadata, but almost every clause carries useful information.

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?

For a paid, annotated, output-schema-backed generation tool, the description supplies the trigger, the exclusions, the cost, the latency, and the output format. Nothing needed to call it correctly is missing, and return values are additionally covered by the output schema.

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 100%, so ecc, border, pixelSize, and response_format are already documented in the schema, and the description only alludes to 'error correction level and border options'. Baseline 3 applies since the schema carries the parameter burden and the description adds no syntax or format detail beyond it.

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?

States a specific verb (generate) and resource (QR code), plus the supported payloads (URL, text, Wi-Fi, payment link) and the output form (SVG). It also carves out what it is NOT for (reading/decoding existing codes, logos, colored codes, PNG), which lets an agent separate it from adjacent media/image tools without opening a schema.

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?

Opens with an explicit 'Use when you need...' trigger and immediately follows with a 'Do not use for...' exclusion list. Both the positive condition and the negative boundary are spelled out, leaving nothing to inference.

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

All Blackwood State tools Inspect

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

Need Help?