Skip to main content
Glama

APEX x402 & AI Agent Tools (360 tools)

Arc poison stats

arc_poison_stats

Free: how much address poisoning is happening on Arc USDC right now (events, lookalike addresses, targeted wallets, kinds), from our live index of every Arc USDC transfer.

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_poison_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose that the tool is free, that it reflects a live index of every Arc USDC transfer, and that the snapshot is current ('right now'). It also enumerates the dimensions reported, which partly substitutes for the missing output schema. It says nothing about result size, refresh cadence, or whether the data is scoped to one chain only, so gaps remain for a zero-annotation tool.

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?

A single sentence with the cost qualifier ('Free') and the temporal qualifier ('right now') front-loaded before the substance. The parenthetical field list is dense but each item adds information. Slight redundancy between 'address poisoning' and 'lookalike addresses', but nothing that should be cut.

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 zero-parameter read tool with no output schema and no annotations, the description covers purpose, data source, freshness, and the shape of the returned metrics, which is close to everything an agent needs to decide to call it. The main missing piece is disambiguation from 'poison_events' and any note on how results are scoped.

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 tool takes no parameters, so there is nothing for the description to disambiguate beyond confirming that no input is required. Baseline of 4 applies for a zero-parameter tool.

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: aggregate address-poisoning statistics on Arc USDC, broken into events, lookalike addresses, targeted wallets, and kinds. The word 'stats' plus the enumerated breakdown makes clear this is an aggregate metrics tool rather than an event lister. It does not, however, name or contrast itself with the sibling 'poison_events', so an agent must infer which of the two returns counts versus individual events.

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?

'Right now' and 'free' imply a monitoring/overview use case with no cost barrier, which is useful selection signal. There is no explicit when-to-use or when-not-to-use statement, and the closely related sibling 'poison_events' is never mentioned as an alternative for per-event detail. Usage is therefore inferable but not stated.

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.