Skip to main content
Glama

Arc smart signals

arc_smart_signals

Smart-money signals on Arc: the 25 most profitable wallets of the last 24 h buying a token in increments (3+ buys or $150+ in 60 min) or together (2+ wallets), only while they still hold half of what they bought (closed as EXITED when they sell), each with their record, a simulated sell check and a staged entry/exit plan with a quarter-Kelly size cap. Not advice. $0.01 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_smart_signals"
  }
}

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

A4.1/5.0
Behavior4/5

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

With no annotations, the description discloses the $0.01 x402 charge, accepted assets and networks, wallet-signing workflow, simulated sell check, position-closure behavior, and quarter-Kelly sizing cap. It would be stronger if it explicitly stated that no trade is executed and clarified whether the initial terms-only call is free, but the principal cost and payment side effect are visible.

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?

The purpose and detection criteria come first, followed logically by the disclaimer, price, and payment workflow. The opening sentence packs many nested thresholds and clauses into a dense whole, reducing scannability, but there is little redundant wording.

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

Completeness5/5

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

For a one-parameter tool without annotations or an output schema, it covers the wallet cohort, time window, trigger thresholds, holding condition, closure behavior, output components, sizing constraint, cost, and invocation sequence. Exact result-field formatting is unstated, but an agent has enough information to decide whether to use the tool and invoke it correctly.

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?

The schema already documents the signed base64 payment payload and in-call purchase completion, so the baseline is covered. The description adds meaningful operational semantics: omit `payment` first to obtain terms, sign those terms with the caller's wallet, and retry with `payment`.

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 identifies a specific Arc analytics resource: signals based on the 25 most profitable wallets over 24 hours, with concrete accumulation triggers and an EXITED lifecycle. This is much clearer than the title, but it does not explicitly differentiate the tool from siblings such as arc_dip_signals, arc_whales, or arc_whale_feed.

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?

The methodology and staged entry/exit plan make the intended smart-money accumulation use case clear, while the final sentence provides precise two-call payment guidance. It does not explain when a dip-signal or whale-related sibling would be preferable, nor give explicit 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