Skip to main content
Glama

scan_living_qr

Read-only

Free. Read an existing Living QR presentation, not a QR generator or x402 purchase. Scan a stored Living QR. GET https://authichain.com/qron/r/{object_id} returns AuthiChain Verification Decision v1. This host verifies the signature. A missing id is presentation_not_found. Not an x402 payment endpoint, and it does not inspect a physical product.

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": {
      "object_id": "<object_id>"
    },
    "name": "scan_living_qr"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_idYesStored presentation id. Canonical form is qron:url: plus 8 hex characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses that the call is free, the exact host and path hit, that the host performs signature verification, the versioned result type returned, and the specific failure mode ('presentation_not_found' for a missing id). This is precisely the extra context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with cost and purpose, but the negatives are duplicated: 'not a QR generator or x402 purchase' is restated as 'Not an x402 payment endpoint'. 'Scan a stored Living QR' also echoes the opening sentence, so a couple of sentences do not earn their place.

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?

For a one-parameter read tool with no output schema, it covers cost, endpoint, verification behavior, and the not-found case. The only gap is the shape of the Verification Decision v1 payload, which an agent must discover at call time.

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 baseline is 3, but the description adds value by embedding {object_id} in the concrete GET path, showing it is a URL path segment, and the schema supplies the canonical 'qron:url:' + 8 hex form. Little more is needed for a single string id.

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 ('Read an existing Living QR presentation') and then fences it off from two look-alikes: a QR generator and an x402 purchase. An agent can separate this from verify/query_provenance siblings without opening any schema.

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?

It clearly states the use case (retrieving a stored presentation) and gives explicit exclusions ('not a QR generator', 'not an x402 payment endpoint', 'does not inspect a physical product'), which effectively routes the agent away from wrong choices. It stops short of naming the sibling tool to use instead for those other cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.