Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

optical_bounty_create

Create an A2A Eyes-on-Street / Eyes-on-Venue optical verification bounty settled on Base Mainnet USDC (payment_proof_token) or authorized sovereign grant.

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": {
      "destination_id": "<destination_id>",
      "site_id": "<site_id>",
      "buyer_agent_id": "<buyer_agent_id>",
      "question": "<question>"
    },
    "name": "optical_bounty_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYes
questionYes
hud_promptNo
target_latNo
target_lonNo
reward_usdcNo
ttl_secondsNo
payment_railNo
buyer_agent_idYes
destination_idYes
geofence_radius_mNo
payment_proof_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the create/non-idempotent profile is covered. The description adds genuine context beyond that by naming the settlement currency and payment_proof_token rail, which signals that real money is committed. It does not say whether funds are escrowed, who is charged, what happens when ttl_seconds expires, or whether retries duplicate bounties despite non-idempotency.

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 front-loaded sentence with no wasted clauses; the action and the settlement mechanism come first. Density of unexplained jargon keeps it from being optimally readable rather than merely short.

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

Completeness2/5

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

This is a 12-parameter, high-stakes creation tool with no output schema and zero schema description coverage, yet the description is one sentence. An agent cannot learn from it what a valid bounty looks like, what the required identifying fields mean, or what it gets back, which is inadequate for this complexity.

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% across 12 parameters, so the description carries the full explanatory burden and largely fails it. It only gestures at payment_proof_token and settlement currency; destination_id, site_id, buyer_agent_id, question, hud_prompt, target_lat/lon, reward_usdc, ttl_seconds, geofence_radius_m and payment_rail are all left to inference. No format, unit, or constraint guidance compensates for the schema gap.

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?

Uses a specific verb ('Create') plus a specific resource ('optical verification bounty'), and names its settlement rail (Base Mainnet USDC / sovereign grant). It is readily distinguishable from the read-side sibling optical_bounty_get. It falls short of 5 because the domain jargon ('A2A Eyes-on-Street', 'sovereign grant') is never unpacked, so the object being created stays partly opaque.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description contains no when-to-use, when-not-to-use, or alternative-selection guidance at all. Nothing says when a bounty should be created versus reading existing ones with optical_bounties/optical_bounty_get, nor what prerequisites exist. Only the tool name implies usage.

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