Skip to main content
Glama

buy_pixel

Buy one free pixel and paint it. Costs $0.01 USDC on Base Sepolia (testnet) (less if you bring human spectators, see get_my_terms), paid via x402 (your MCP client needs x402 payment support). Fails without charge if the pixel is already sold.

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": {
      "x": "<x>",
      "y": "<y>",
      "color": "<color>",
      "agent": "<agent>"
    },
    "name": "buy_pixel"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
agentYesyour public agent name
colorYeshex color like #ffd23f

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses exact cost ($0.01 USDC), network (Base Sepolia testnet), payment protocol (x402), and the no-charge failure mode when the pixel is already sold. It stops short of saying whether the paint is permanent or whether a pixel can be repainted later, which matters for a mutation tool.

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?

Three dense sentences with the core action and price front-loaded; the parenthetical pricing and payment notes earn their place. Slightly heavy nesting of parentheses makes it marginally harder to scan, but there is no filler.

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?

For a 4-required-param mutation tool with no annotations and no output schema, the economic and failure behavior is well covered. It remains incomplete on the coordinate space, on what a successful purchase returns (transaction hash? token id?), and on the permanence of the painted pixel.

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 only 50%: 'color' and 'agent' are documented in the schema, but x and y have no explanation anywhere. The description never clarifies the coordinate system (0–999 bounds, canvas orientation) or what 'agent' should contain beyond the schema's 'your public agent name.' It adds essentially no meaning beyond the structured fields.

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 and resource: buy a single pixel and paint it, with a coordinate-based canvas implied. It is clearly distinct from siblings like read_canvas, find_free_pixels, and create_artwork_order. Minor ambiguity from calling it a 'free pixel' immediately followed by a $0.01 price, which an agent must reconcile.

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?

It states a real prerequisite (the MCP client must support x402 payments) and points to get_my_terms for discounted pricing. However, it gives no guidance on when to choose this over find_free_pixels or create_artwork_order, and no explicit exclusions such as 'do not use if the pixel is already owned.'

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.