Skip to main content
Glama

sol_pre_trade_bundle

Read-onlyIdempotent

The whole Solana stack in one call — gate + safety + holders + market — One call returns everything a Solana agent needs before a buy: a GO / HOLD / STOP gate, the full safety verdict (authorities, Token-2022 seize extensions, sellability, LP-lock), top-10 holder concentration, and market depth (price, liquidity, 24h volume). Fewer round-trips than calling each check. An unreadable gating read is UNKNOWN, not charged. Not advice. Required input: mint. Priced $0.05 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_bundle"
  }
}

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.4/5.0
Behavior5/5

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

Beyond the supplied readOnly/idempotent/non-destructive annotations, the description discloses the payment model ($0.05 per call via x402 on Base), the prepaid x-credit-token path, the free-tier limit, no-API-key access, and the important billing edge case that an unreadable gating read returns UNKNOWN and is not charged. These are material behaviors an agent cannot infer from the schema or annotations.

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 core value ('whole stack in one call') is front-loaded, followed by the enumerated outputs; the pricing and payment details are dense but earn their place for a paid endpoint. It is slightly long, with the payment/billing sentence packing several facts, but nothing is pure filler.

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 paid aggregation tool with an output schema, this covers purpose, return components, billing, error semantics (UNKNOWN), and required input; the presence of an output schema means return values needn't be detailed further. Nothing an agent needs to invoke it 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?

There is a single parameter (mint) at 100% schema coverage, and the description only restates 'Required input: mint' without adding format, network, or validation detail. Per the high-coverage baseline, a 3 is appropriate since the schema already carries the semantics.

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 specific resource and an aggregated action: 'The whole Solana stack in one call — gate + safety + holders + market,' then enumerates exactly what each component yields (GO/HOLD/STOP gate, safety verdict, top-10 concentration, market depth). This distinguishes it clearly from the single-purpose siblings like sol_price, sol_sellability, and sol_token_risk.

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 concrete trigger ('everything a Solana agent needs before a buy') and a comparison to alternatives ('Fewer round-trips than calling each check'), which tells the agent when the bundle beats individual calls. It does not explicitly name which sibling to fall back to when only one check is needed, so it stops short of full 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