Skip to main content
Glama

Arc fee flow

arc_fee_flow

Arc launchpad fee vaults: every vault holding USDC now, its creator and token, and how much it changed since our previous scan. Fees only accrue from real swaps. $0.025 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_fee_flow"
  }
}

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.8/5.0
Behavior3/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 disclose the key traits: the tool is paywalled, costs $0.025 per call, accepts specific assets/chains, and requires a two-step sign-then-submit flow. It omits whether the call is read-only safe (implied), rate limits, staleness of "our previous scan," and failure behavior when payment is invalid.

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?

Three sentences, front-loaded with what the agent gets, followed by price and the call sequence; almost nothing is wasted. The opening noun-phrase fragment and the dense parenthetical of accepted assets are slightly compressed but still readable.

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?

There is no output schema, so the description appropriately describes the returned fields (vault, creator, token, delta) and explains how fees accrue. For a one-parameter paywalled read tool this covers what an agent needs, though it leaves the granularity/units of the change figure and payment-failure behavior unstated.

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 single `payment` parameter is already documented, but the description adds the genuinely useful protocol: omit it for terms, then pass the signed base64 x402 payload to complete the purchase inside the call. That is meaning beyond the schema's restatement of PAYMENT-SIGNATURE.

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 the resource concretely (launchpad fee vaults holding USDC, their creator and token, and the delta since the previous scan), so an agent knows exactly what data comes back. It does not explicitly contrast itself with near neighbors like arc_x402_stats or arc_pools, which keeps it short of a 5.

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?

It gives an explicit operating procedure: call once with no `payment` to receive terms, sign with your own wallet, then call again with `payment` to complete the purchase. It also states the price and accepted payment assets. It does not say when to prefer this over other arc_* data tools, but the invocation guidance is unusually concrete.

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