Skip to main content
Glama

Fuci on arc

fuci_on_arc

Fuci on Arc, read from the chain every 10 minutes: every Uniswap v4 pool paired with the REAL $FUCI (0xE66d...4420) with its class (launch = made through Fuci's launchpad; high-fixed-fee = a FIXED fee of 10% or more on every trade, where a routed buy loses that share), live liquidity and price; every $FUCI burn checked against the claim that fees burn it every day; and the tokens that call themselves FUCI but are not. $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": "fuci_on_arc"
  }
}

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.7/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 does substantial work: 10-minute refresh cadence, a paid x402 model at $0.003 per call, accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and a two-phase handshake before data is returned. What is missing is failure behavior — e.g. what happens if the signed payment is expired or underfunded, or whether repeated unpaid calls are throttled.

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?

It opens by restating the tool name and is written as a long chain of clauses rather than discrete statements, so the payment mechanics — arguably the most important part — land at the very end. The parenthetical explaining 'high-fixed-fee' classes is genuinely useful, but phrases like 'the REAL $FUCI' are promotional filler that consume space without informing an agent.

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 read tool with no output schema and no annotations, the description covers the data returned, freshness, cost, payment rails, and the payment handshake — enough for an agent to invoke it correctly. Only the absence of error/rate-limit behavior and sibling disambiguation keeps it short of complete.

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%, so the baseline is 3. The description adds real meaning beyond the schema by explaining the parameter's role in the overall flow: omitting it yields terms, supplying the signed payload completes the purchase inside the same call — semantics the schema text only partially conveys.

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 states a specific verb ('read from the chain every 10 minutes') and specific resources: Uniswap v4 pools paired with $FUCI 0xE66d...4420, burn verification, and impostor tokens. The marketing framing ('REAL $FUCI') slightly muddies it, and it never names how it differs from overlapping siblings like arc_impostors or arc_token_info, but the subject matter is unmistakable.

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?

It gives an explicit invocation protocol — call once without `payment` to get terms, sign with your own wallet, call again with `payment` — which is genuinely actionable. However, it gives no guidance on when to choose this over the many sibling tools covering FUCI pools, burns, or impostors (arc_impostors, arc_pools, arc_token_info), leaving that inference entirely to the agent.

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