Skip to main content
Glama

sol_pre_trade_gate

Read-onlyIdempotent

GO / HOLD / STOP for any SPL token — the call every bot makes before it buys — The one call a Solana trading agent makes before each buy: GO / HOLD / STOP for any SPL mint, with the reasons and a recommended max size. Distils the full safety stack (mint/freeze authority, Token-2022 seize extensions, Jupiter sellability, RugCheck LP-lock) into a single trade decision. STOP on any terminal flag (seize, honeypot, freeze-trap). Unverified mint is UNKNOWN, not charged. Not advice. Required input: mint. Priced $0.04 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_pre_trade_gate"
  }
}

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.2/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the terminal-flag STOP rule, the UNKNOWN-not-charged behavior for unverified mints, and full payment/auth mechanics ($0.04/call over x402, prepaid x-credit-token header, 1 free call/day, no API key). What it does not disclose is latency, caching/freshness of the underlying safety signals, or failure behavior when a data source is unavailable.

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-loaded with the decision framing and the STOP rule before the pricing boilerplate, which is the right order. The opening two clauses ('the call every bot makes before it buys' and 'The one call a Solana trading agent makes before each buy') say the same thing twice and could be merged.

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?

An output schema exists, so return values need not be spelled out, and the description still supplies decision semantics, the negative/unknown case, and the payment model. For a one-parameter read-only gate this covers everything an agent needs before invoking.

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, already documented at 100% schema coverage ('Solana SPL mint address'), and the description merely restates it as 'Required input: mint'. No added semantics such as accepted formats or behavior for malformed/non-SPL addresses, so the schema does the work.

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?

States a concrete verb and output (GO/HOLD/STOP decision), a concrete resource (any SPL mint), and the composite scope (mint/freeze authority, Token-2022 seize, Jupiter sellability, RugCheck LP-lock) that separates it from single-signal siblings like sol_liquidity or sol_sellability. An agent knows exactly what it gets back and for what asset.

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?

Usage timing is explicit: 'the call every bot makes before it buys' / 'before each buy', and the STOP rule defines the decision threshold. It stops short of naming alternatives (e.g., when to reach for sol_token_risk or sol_token_verdict for deeper detail) or stating when this tool is unnecessary.

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