Skip to main content
Glama

Arc token compare

arc_token_compare
Read-onlyIdempotent

Side-by-side comparison of 2 to 4 Arc token contracts: liquidity, exit checks, holders, and pool state. $0.005 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": {
      "tokens": "<tokens>"
    },
    "name": "arc_token_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokensYes2 to 4 different comma-separated Arc token addresses (0x + 40 hex)
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.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so safety is covered. The description adds genuinely new behavioral context: cost ($0.005 per call), the x402 payment rail (USDC on Arc/Base/Solana, XNT on X1), and the two-phase terms-then-pay protocol that governs how a paid call actually completes. It does not describe the shape or size of the comparison result, which matters for a paid call.

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?

Two sentences, both dense with distinct information: first the capability, then the paid-invocation mechanics. Nothing repeats the title, and the scope is front-loaded ahead of the payment details.

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 read-only, two-parameter tool with full schema coverage, the description covers purpose, cost, and auth flow adequately. Since there is no output schema, it should say more about what the comparison returns (a table, per-metric verdicts, or ranked results), because the agent is paying per call and needs to know what it gets.

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 the baseline is 3, but the description adds real meaning: it explains what the `payment` parameter represents procedurally (obtain terms unsigned, sign externally, resubmit) rather than just restating the schema's one-line definition. It also restates and reinforces the 2-to-4 constraint on `tokens`.

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?

A specific verb ('Side-by-side comparison') plus resource ('Arc token contracts'), with cardinality ('2 to 4') and the compared dimensions (liquidity, exit checks, holders, pool state). The '2 to 4 side-by-side' framing implicitly separates it from single-token siblings like arc_token_check and arc_token_info, though no sibling is named explicitly.

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 operational guidance for the awkward case: call once without `payment` to obtain terms, sign them with your own wallet, then call again with `payment`. It does not say when to prefer this over a single-token check or when a comparison is not appropriate, so it stops short of full alternative routing.

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