Skip to main content
Glama

Arc cost

arc_cost

Estimated transaction and gas cost breakdown across Arc mainnet routes. $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_cost"
  }
}

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.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the burden and does meaningful work: it discloses the paid x402 model, the exact price ($0.003 per call), the accepted payment assets and chains (USDC on Arc/Base/Solana, XNT on X1), and that the purchase completes inside the call when `payment` is supplied. It stops short of covering failure modes, e.g. what happens if an unsigned call's terms expire or the payment is rejected.

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

Conciseness5/5

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

Three tight sentences: purpose first, pricing second, invocation flow third. No filler, and the most decision-relevant facts (what it returns and what it costs) are front-loaded.

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 one-parameter tool with no output schema and no annotations, it covers cost, payment mechanics, and the handshake well. The remaining gap is the return shape: 'breakdown' is never unpacked, so an agent doesn't know whether it gets per-route line items, gas components, or a single total, which matters since no output schema exists.

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% and the schema already explains `payment` as a signed x402 base64 payload equivalent to PAYMENT-SIGNATURE. The description adds real meaning beyond that by explaining how to obtain the payment (first call returns terms, you sign them, second call settles), which the schema alone does not convey.

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?

States a specific verb and resource: 'Estimated transaction and gas cost breakdown across Arc mainnet routes.' An agent can tell this computes cost estimates, though it never differentiates itself from siblings like arc_gas or arc_cctp_cost, which plausibly overlap.

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?

Gives a clear two-step invocation procedure (call without `payment` for terms, sign with your own wallet, call again with `payment`) and states the price. However, it offers no guidance on when to pick this tool over arc_gas or arc_cctp_cost for cost questions, so alternative selection is left to inference.

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