Skip to main content
Glama

Commodity board

commodity_board
Read-onlyIdempotent

Free sample: https://apexfaucet.xyz/citizens/forge/ ($0.002). Commodity AMM pool counts and locked amounts from the forge page. Not a swap. Not advice. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "commodity_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Beyond the supplied annotations, the description discloses the paid x402 model, accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), the price, and that the purchase settles inside the tool call. That is real added context. It says nothing about failure modes, expiry of signed terms, or whether a re-call without payment re-issues terms, which matters for an open-world paid tool.

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?

The payment flow is front-loaded reasonably well, but the opening sample link and the price, stated twice ($0.002), are commercial padding rather than invocation guidance. Multiple short fragments ("Not a swap. Not advice.") read as marketing copy instead of structured guidance.

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 single optional parameter, no output schema, and a read-only board, the definition covers the payment handshake, the content returned (pool counts and locked amounts), and the disclaimers an agent needs. Remaining gaps are response shape and what "locked amounts" precisely measures, both minor here.

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% and the schema already explains `payment` as the base64 payload for PAYMENT-SIGNATURE. The description adds the two-step negotiation semantics (the parameter is only supplied on the second call), which is useful. It does not detail payload format, TTL, or accepted network selection beyond the rail list.

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 core sentence, "Commodity AMM pool counts and locked amounts from the forge page," names a specific resource and payload, and "Not a swap" explicitly separates it from the swap-building sibling. The clarity is partly undercut by the leading ad-style sample link and price, which precede the actual purpose statement.

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 gives an unusually explicit call sequence: call once without `payment` to get terms, sign them with your own wallet, then call again with `payment`. It also states what the tool is not (not a swap, not advice), steering agents away from a wrong use. It stops short of naming which sibling to use instead for swaps or pricing.

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