Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

optical_bounty_get

Read-onlyIdempotent

Retrieve an A2A optical verification bounty record and its detached Ed25519 VisualEvidenceReceipt by bounty_id.

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": {
      "bounty_id": "<bounty_id>"
    },
    "name": "optical_bounty_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
bounty_idYes
include_redacted_previewNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description does add genuine value by disclosing that the response bundles a detached Ed25519 VisualEvidenceReceipt alongside the record, but it says nothing about verification expectations, not-found behavior, or what the redacted preview actually redacts.

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?

A single well-formed sentence with the action verb front-loaded and no filler. It is efficient, but the noun pile-up ('A2A optical verification bounty record ... detached Ed25519 VisualEvidenceReceipt') packs several distinct concepts into one clause that could be parsed more cleanly.

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

Completeness3/5

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

With no output schema, the description does useful work by naming the two payload components returned. However, for a lookup tool with a cryptographic receipt component, it omits not-found/error semantics and entirely ignores one of its two parameters, leaving an agent under-informed on the edges.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, so the description must carry the burden and largely does not. It only restates bounty_id (already constrained by the ^bty_[a-f0-9]{16}$ pattern in the schema) and leaves include_redacted_preview completely unexplained — an agent cannot tell what enabling it returns or what gets redacted.

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?

The description gives a specific verb ('Retrieve') plus a precisely scoped resource ('A2A optical verification bounty record and its detached Ed25519 VisualEvidenceReceipt') keyed by bounty_id. It is clearly a single-record fetch rather than the listing implied by the sibling name optical_bounties, though it never names that sibling explicitly and the terminology is dense.

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 only implied: 'by bounty_id' signals the caller must already hold a bty_ identifier, which indirectly means this is a lookup-after-create/list operation. There is no explicit statement of when to prefer this over optical_bounties or optical_bounty_create, and no mention of what happens if the id is unknown.

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.

Resources