Hovercode

download_qr

Read-onlyIdempotent

Get downloadable, print-ready image links for a QR code — a high-resolution PNG and a vector SVG (best for print/large sizes). Returns URLs you can share or save.

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": {
      "id": "<id>"
    },
    "name": "download_qr"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	QR code id.

Output Schema

Name	Required	Description
`id`	No
`error`	No	Present only when the tool failed (isError): cause, retryable, message.
`png_url`	No	Print-ready PNG; null if rendering failed.
`svg_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 13, 2026

removedOutput schema / properties / error / additionalProperties
```
Removed value: -true
```

changedOutput schema / properties / error / description

Previous value: -"Present only when the tool failed (the result is also flagged isError)."New value: +"Present only when the tool failed (isError): cause, retryable, message."

removedOutput schema / properties / error / properties

Removed value: -{
-  "cause": {
-    "description": "Machine-readable failure category: invalid_argument, not_found, forbidden, plan_limit, rate_limited, or server_error.",
-    "type": "string"
-  },
-  "message": {
-    "type": "string"
-  },
-  "retryable": {
-    "description": "Whether repeating the same call could succeed.",
-    "type": "boolean"
-  }
-}

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "error": {
+      "additionalProperties": true,
+      "description": "Present only when the tool failed (the result is also flagged isError).",
+      "properties": {
+        "cause": {
+          "description": "Machine-readable failure category: invalid_argument, not_found, forbidden, plan_limit, rate_limited, or server_error.",
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retryable": {
+          "description": "Whether repeating the same call could succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "id": {
+      "type": "string"
+    },
+    "png_url": {
+      "description": "Print-ready PNG; null if rendering failed.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "svg_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the output nature — print-ready high-res PNG and vector SVG URLs that can be shared or saved — which tells the agent what the response actually is. It omits URL expiry, auth, or rate-limit behavior.

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?

Two tight sentences, front-loaded with the action and capped by the return type. The em-dash aside on PNG vs SVG earns its place by clarifying print use cases; no filler.

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?

With an output schema present, the description needn't detail return values, and it adequately frames a simple single-parameter read tool. Minor gap: it never hints where the required id comes from among the many sibling listing tools.

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% with a single 'id' parameter already described as 'QR code id.' The description says nothing further about the identifier (e.g., where to obtain it), so the schema carries the full load; baseline 3 is appropriate.

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?

States a specific verb and resource — retrieve downloadable image links for a given QR code — plus the exact artifacts (high-resolution PNG, vector SVG). It is clear what an agent gets back. It does not explicitly distinguish itself from near-neighbors like create_pdf_qr or get_qr_code, so it falls short of a 5.

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 rather than stated: an agent can infer 'call this when you need image files.' The parenthetical 'best for print/large sizes' gives a useful format-selection cue, but there is no explicit when-to-use/when-not and no alternative tool is named.

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

All Hovercode 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.