Skip to main content
Glama

Arc bundle check

arc_bundle_check

Was this Arc launch bundled? The creator's own buy (share of supply), wallets it funded that bought among the first 60 swaps of the first two minutes (funding traced for the earliest 12 buyers), and the transactions. Pass token or pool. $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_bundle_check"
  }
}

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

B3.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly succeeds: it discloses price, accepted payment assets (USDC on Arc/Base/Solana, XNT on X1), and the two-call x402 handshake needed before a paid call completes. It also exposes analytic limits (funding traced only for the earliest 12 buyers, first 60 swaps, first two minutes), which is real behavioral context rather than a restatement of the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the key question, which is good, and the payment flow is sequenced logically. The middle sentence is a dense run-on that crams three distinct outputs together, and the stray "Pass token or pool" clause adds noise without adding usable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The central practical question — how do I tell the tool which token or pool to check? — is unanswered: the schema exposes only `payment`, no token, pool, or address field. An agent can complete the payment dance but has no documented way to scope the analysis, which is a fatal gap for a per-launch check with no output schema to compensate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the `payment` parameter is well documented in-schema, so the baseline would be 3. But the description introduces "Pass token or pool" when no such parameter exists in the schema, sending the agent looking for inputs it cannot supply. That ambiguity outweighs the useful payment-flow elaboration.

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?

"Was this Arc launch bundled?" states the resource and the question it answers, and the follow-up lists the concrete evidence returned (creator buy share, funded wallets among first 60 swaps, transactions). That is specific enough to distinguish it from siblings like arc_fresh_launches or arc_trades, though it never names those alternatives explicitly.

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?

The payment guidance is genuinely actionable: call once without `payment` for terms, sign with your own wallet, call again with `payment`, at $0.004/call. But there is no guidance on when to use this versus sibling checks (arc_contract_check, arc_trades, arc_fresh_launches), and "Pass token or pool" is left hanging without saying where.

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