Skip to main content
Glama

sol_sellability

Read-onlyIdempotent

Can you SELL it back, or is it a honeypot? — Probes a real sell route back to USDC (Jupiter) for any SPL mint: sellable or not, price impact, and a HONEYPOT flag when it's buyable but has no sell route AND an active freeze authority. The check sniper bots make before buying. Unreadable mint or no Jupiter answer → not charged. Not advice. Required input: mint. 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": {
      "mint": "<mint>"
    },
    "name": "sol_sellability"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana SPL mint 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/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, yet the description still adds substantial behavior: honeypot is defined precisely (buyable but no sell route AND active freeze authority), failures are explicitly not charged, and the full billing model is disclosed (x402 on Base at $0.02/call, prepaid x-credit-token header for unlimited, 1 free call/day, no API key). That is more than the annotations carry.

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 opening question-plus-answer framing front-loads value and the middle is dense with concrete facts. It is slightly overstuffed, mixing purpose, output semantics, failure billing, pricing, auth, free tier and a disclaimer into one run-on block, but almost every clause carries information an agent needs.

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?

Given an output schema exists, return-value explanation is a bonus rather than a requirement, yet the description still surfaces the key result fields. Combined with cost, auth path, free-tier limits, and failure-charging semantics, nothing an agent needs to invoke this tool correctly is missing.

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?

Schema coverage is 100% and the single parameter already documents 'Solana SPL mint address'. The description only restates it as 'Required input: mint', adding no format, chain, or validity detail beyond the schema, so the baseline 3 applies.

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?

States a concrete action (probe a real sell route back to USDC via Jupiter) against a specific resource (any SPL mint) and names the three things it determines: sellability, price impact, and a honeypot flag. The Solana/SPL scoping implicitly separates it from the broader sibling set, but the near-identically named sibling 'sellability' is never addressed, so the agent gets no explicit disambiguation.

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 check sniper bots make before buying' implies a pre-trade use case, which is real guidance. However, there is no explicit when-not guidance, no prerequisites stated, and no pointers to the closely related siblings (sol_pre_trade_gate, sol_token_risk, sellability) that an agent would need to choose between.

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