Skip to main content
Glama

Arc price at

arc_price_at

Historical token prices on Arc, batch: up to 50 token@block pairs, each priced from its deepest Uniswap v4 USDC pool AT that block. For history values, P&L, tax exports. Not one priceable pair = refused before payment. $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

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": {
      "q": "<q>"
    },
    "name": "arc_price_at"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYescomma-separated 0xTOKEN@BLOCK pairs, up to 50
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

A4.3/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 the pricing source, the 50-pair cap, an all-or-nothing refusal rule that fires before payment, per-call cost ($0.003), and accepted payment rails. It leaves open what happens when only some pairs are priceable and what the response contains, which keeps it from a 5.

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?

Front-loaded with purpose, then use cases, then the payment mechanics, with no filler. The telegraphic fragments ('Not one priceable pair = refused before payment') are efficient but slightly terse, costing a little readability.

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 simple two-parameter, no-output-schema tool, the critical unknowns (source of truth, batch limit, payment flow, refusal behavior, cost) are all covered. A short note on the returned per-pair structure would close the remaining gap, but nothing essential for invoking it correctly is missing.

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%, so baseline is 3, but the description genuinely adds meaning: `q` pairs are priced at the given block against the deepest Uniswap v4 USDC pool, and `payment` is explained as the second half of an x402 handshake that completes the purchase in-call. That is context the schema fields alone do not convey.

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

Purpose5/5

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

States a specific verb and resource ('Historical token prices on Arc'), the batching model ('up to 50 token@block pairs'), and the exact pricing source ('deepest Uniswap v4 USDC pool AT that block'). The word 'Historical' plus 'AT that block' implicitly separates it from the spot-price sibling arc_price without needing to open either schema.

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?

Gives concrete use cases ('history values, P&L, tax exports') and an explicit invocation workflow: call without `payment` for terms, sign with your own wallet, call again with `payment`. It stops short of naming alternatives such as arc_price for current prices or arc_impact, so the when-not guidance is left implicit.

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