Skip to main content
Glama

Arc deployers

arc_deployers

Who launched what on Arc and whether any of it ever traded: every repeat creator with their launches and the swap fees those launches earned. $0.004 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_deployers"
  }
}

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 full burden and does substantial work: it discloses the price ($0.004 per call), accepted payment currencies and chains, and the exact two-step signed-payment handshake needed to complete a call. It stops short of describing result shape, ordering, or whether coverage is time-bounded, which are the remaining behavioral gaps for a paid analytics tool.

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 compact sentences: the first front-loads what the tool returns, the second front-loads cost and then the call sequence. No filler, no restatement of the tool name, and the payment mechanics are ordered the same way an agent would execute them.

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 and no annotations, and the description compensates by describing both the semantic content of the result ('repeat creator with their launches and the swap fees those launches earned') and the full payment protocol. Completeness would be higher if it hinted at result size, ordering, or what an empty result means for a paid call.

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 already 100% for the single `payment` parameter, so the baseline is 3. The description earns extra credit by explaining the two-phase acquisition pattern — first call returns terms, second call with the signed payload completes the purchase — which is workflow meaning not captured in the schema's one-line property description.

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 uses a specific framing ('every repeat creator with their launches and the swap fees those launches earned') that clearly identifies the resource: deployer/creator history with fee aggregation. It distinguishes the shape of the data but never names or contrasts with adjacent siblings like arc_fresh_launches, arc_graveyard, or arc_trending, so the agent must infer the difference.

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?

Usage guidance is present but almost entirely about the x402 purchase protocol ('call once without `payment` for the terms, sign them with your own wallet, call again with `payment`'), not about when this tool is the right choice over alternatives. There is no statement of when to prefer deployer data over launch feeds or graveyard data, and no exclusions.

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