Skip to main content
Glama
Sign In

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Solana token pre-trade check

get_sol_token_check
Read-onlyIdempotent

Use when an agent needs a pre-trade check on a Solana token. Returns mint and freeze authority, Token-2022 traps, top holders, deepest pool and USD depth, the price impact of $100 and $1,000 buys, pump.fun progress, and a verdict with every rule. Costs 0.025 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

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": "get_sol_token_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesthe SPL token mint address

Output Schema

NameRequiredDescriptionDefault
dataYesthe get_sol_token_check payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_sol_token_check
toolYesthe tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / mint / maxLength
      Added value: +44
    • addedInput schema / properties / mint / minLength
      Added value: +32
    • addedInput schema / properties / mint / pattern
      Added value: +"^[1-9A-HJ-NP-Za-km-z]{32,44}$"
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior, while the description adds important non-schema context: a cost of 0.025 USDC per call and supported x402 payment chains. It also describes the returned signals, though it does not mention rate limits or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the usage condition, and every clause contributes either invocation guidance, returned-signal scope, or cost. There is no redundant restatement of the name or schema.

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?

The tool has one fully documented parameter, an output schema, and annotations covering safety behavior; the description still adds the crucial pricing and payment-rail details. Nothing essential for deciding to invoke it or understanding the per-call cost 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?

There is one required parameter, mint, and schema description coverage is 100%, so the input schema already fully documents it. The description adds no additional meaning about the mint parameter beyond indicating that the token is on Solana.

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 and resource: a pre-trade check on a Solana token, and enumerates the outputs it returns. This clearly tells an agent what the tool does, though it does not explicitly distinguish it from nearby sibling tools such as get_token_risk or get_honeypot_check.

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?

It gives an explicit usage context: 'Use when an agent needs a pre-trade check on a Solana token.' However, it does not say when not to use it or name alternative sibling tools for related checks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentFeed toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources