Skip to main content
Glama

Arc creator history

arc_creator_history
Read-onlyIdempotent

Launch history and prior token outcomes for an Arc deployer/creator wallet address. $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": {
      "creator": "<creator>"
    },
    "name": "arc_creator_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
creatorYesArc creator address (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.9/5.0
Behavior3/5

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

Annotations already declare a safe, idempotent, open-world read. The description adds pricing ($0.003 per call), accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and a mandatory two-step handshake, none of which appear in the annotations. It does not describe what the 'launch history' payload contains or how large it may be.

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?

Three sentences: purpose first, cost and rails second, the calling protocol third. Nothing is redundant, and the most decision-relevant facts are front-loaded.

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?

With no output schema, the description should say what the results are, and it states launch history and prior token outcomes, which is enough for an agent to judge relevance. The payment protocol is fully covered. Only the shape or volume of the returned history is left unspecified.

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 explains the payment parameter's role in the two-call protocol rather than merely restating that it is a signed x402 payload. The creator parameter's address format is left entirely to the schema.

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 resource and scope: 'Launch history and prior token outcomes for an Arc deployer/creator wallet address.' That tells an agent exactly what comes back, and the 'Arc' qualifier implicitly separates it from the x1_creator_history sibling. It stops short of explicitly stating how it differs from arc_wallet_history or arc_deployers.

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 a concrete operational workflow: call once without `payment` to get terms, sign, then call again with `payment`. That is real when/how guidance for the purchase path. It offers no guidance on choosing this tool over sibling history or deployer tools, which is the main gap.

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