Skip to main content
Glama

Arc bridge board

arc_bridge_board
Read-onlyIdempotent

Free sample: https://apexfaucet.xyz/arc/bridges/ ($0.003). Cached 2 USDC quotes into Arc from the bridges page. Does not send. Not advice. $0.003 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": "arc_bridge_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

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with them ("Does not send"). Beyond that it discloses real behavioral context the annotations cannot: the $0.003 per-call price, payable over x402 in USDC on Arc/Base/Solana or XNT on X1, and that the two-step unsigned-then-signed flow is required. Return contents and cache staleness remain undisclosed.

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

Conciseness2/5

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

The description opens with an advertising link rather than the tool's function, repeats the $0.003 price twice, and inserts "Not advice" filler. The useful core (cached USDC bridge quotes, does not send, x402 two-call flow) is present but scattered across promotional noise.

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 one parameter, full schema coverage, and no output schema, the priced two-call flow is adequately covered, but the description never says what the quotes actually contain (routes, fees, sizes) or how stale the cached data is, which matters for a quotes board. It is minimally sufficient rather than complete.

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% with a single documented `payment` parameter, so the schema baseline already does the heavy lifting. The description still adds value by explaining the whole negotiation sequence the parameter drives: calling without `payment` yields terms, the caller signs with their own wallet, and the second call with `payment` completes the purchase in-band.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence "Cached 2 USDC quotes into Arc from the bridges page" conveys that this returns bridge quotes for USDC into Arc and does not send anything, but it is grammatically mangled and ambiguous (two quotes? two USDC?), and it never distinguishes the tool from siblings like arc_bridges or bridge_assets. The actual purpose is also buried behind a promotional URL in the first sentence.

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 only usage instruction is the payment handshake ("Call once without `payment` for the terms ... call again with `payment`"), which explains how to pay, not when to choose this board over the many sibling board/bridge tools. There is no stated condition, prerequisite, or exclusion that would let an agent route correctly.

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