Skip to main content
Glama

Arc gold

arc_gold

Verify tokenized gold (XAUm) liquidity, copy tokens, pool fees, and price vs world gold on Arc ($0.003). $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_gold"
  }
}

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 supplied, the description must carry the full burden, and it discloses the cost ($0.003 per call), the payment rail (x402 with USDC on Arc/Base/Solana or XNT on X1), and that passing the payment payload completes the purchase inside the call. These are non-obvious traits an agent cannot infer from the schema. It does not state what the first, unpaid call returns beyond 'the terms', nor whether the price is dynamic.

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?

Two dense sentences, front-loaded with the data being purchased and followed by the payment mechanics. The price '$0.003' is stated twice (once parenthetically after Arc, once as 'per call over x402'), which is mild redundancy, but no sentence is wasted.

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 tool, the description covers cost, payment rails, and the exact call sequence needed to succeed. The main gap is the shape of the unpaid response ('the terms'), which an agent must inspect before signing. Overall complete enough to invoke correctly.

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?

There is a single parameter at 100% schema description coverage, so the baseline is 3. The schema already explains that `payment` is a signed x402 payload that completes the purchase. The description reinforces this and adds the two-call negotiation sequence, but adds no new detail about the payload format itself.

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 description names a specific verb ('Verify') and enumerates the exact resource set: XAUm liquidity, copy tokens, pool fees, and price vs world gold on Arc. An agent knows precisely what data this returns. It does not reference any sibling, but its subject matter is narrow enough that confusion is unlikely.

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?

The two-step invocation is spelled out explicitly: 'Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`.' That is clear operational context for the only real decision point. There is no when-not-to-use guidance, but no plausible alternative tool competes here.

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