Skip to main content
Glama

arb_sellability

Read-onlyIdempotent

Can you SELL it back, or is it a honeypot? — Honeypot / can-you-sell check for any Arbitrum token (GoPlus): sellable or not, sell tax, and a HONEYPOT flag when the contract blocks selling. The check a sniper bot makes before buying. No GoPlus answer → not charged. Not advice. Required input: address. Priced $0.02 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

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": {
      "address": "<address>"
    },
    "name": "arb_sellability"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesArbitrum token address

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the data source (GoPlus), the failure/billing policy ('No GoPlus answer → not charged'), the full payment model ($0.02/call over x402 on Base, prepaid x-credit-token header, 1 free call/day, no API key), and a non-advice disclaimer. Annotations already cover read-only/idempotent safety, and the description adds the commercially important behavior on top.

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?

Front-loads the core question and the HONEYPOT verdict, then layers outputs, failure policy, and pricing. Dense but readable; the pricing/auth sentence is long but earns its place for an agent that must handle payment, and 'Not advice.' is a cheap but deliberate disclaimer.

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 single-input read-only check with an output schema and full annotations, the description covers everything an agent needs: chain scope, what is returned, what happens on no-data (not charged), and how billing/auth works. Nothing material is left to inference.

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

Parameters3/5

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

Only one parameter and schema coverage is 100% ('Arbitrum token address'), so the schema already carries the semantics. The description restates 'Required input: address' but adds no format, validation, or chain-disambiguation detail beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific check ('Honeypot / can-you-sell check') on a specific resource ('any Arbitrum token'), plus the concrete outputs (sellable flag, sell tax, HONEYPOT flag). The chain qualifier ('Arbitrum') implicitly separates it from the generic 'sellability' and 'sol_sellability' siblings without needing to name them.

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 clear use context — 'The check a sniper bot makes before buying' — which tells an agent this is a pre-trade gate. It does not state explicit exclusions or point to alternatives (e.g. when to prefer arb_token_risk or arb_token_verdict instead), so it stops short of full when/when-not guidance.

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