Skip to main content
Glama

Trading Signals Toolkit

Token Pre-Trade Pack

token_pre_trade
Read-only

One GO / CAUTION / STOP status for a token: the Solana or Base token safety verdict, an OFAC sanctions screen of the token's mint/freeze authority or owner and of an optional counterparty wallet, and that wallet's pay-readiness (balances, canPay, shortfalls, approvals) for a USDC amount, with plain reasons. Combines those checks in one call. Heuristic, not an audit or legal advice. Read-only, never places orders. Informational only, not investment advice.

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": {
      "token": "<token>"
    },
    "name": "token_pre_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoToken chain (default: detected from the address)
tokenYesSolana mint (base58) or Base ERC-20 address (0x…), e.g. DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263 for BONK
amountNoUSDC the wallet wants to pay (default 1; needs wallet)
walletNoOptional counterparty or paying wallet (Base 0x… or Solana base58)
walletChainNoWallet chain (default: detected)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true and idempotentHint=false, so safety is partly covered; the description still adds real value by disclosing the epistemic limits ("Heuristic, not an audit or legal advice"), that it never places orders, and that the output carries "plain reasons" alongside the verdict. With no output schema, it reasonably characterizes the return shape. It stops short of noting latency/cost of the live OFAC lookup or what happens when the optional wallet is omitted, keeping it below a 5.

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 single status verdict, then the component checks, then caveats — a sensible order for a decision tool. It is a dense single block with mild redundancy in the disclaimers ("not an audit or legal advice" plus "Informational only, not investment advice"), which could be tightened but each clause still carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter, fully documented, read-only composite with no output schema, the description covers inputs (chain, token, optional wallet, USDC amount), the output verdict and reasons, and the honesty caveats. The remaining gap is behavioral: it does not say what the verdict returns when no wallet is supplied or how it degrades when one chain's data is unavailable.

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 description coverage is 100%, and the schema already spells out chain defaults, address patterns, the 1 USDC default amount and the "needs wallet" dependency, so the schema does the heavy lifting. The description adds framing (amount is what the counterparty wallet would pay; wallet is optional) but repeats rather than extends the schema's semantics. Baseline 3 applies.

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?

The description names a concrete deliverable ("One GO / CAUTION / STOP status for a token") and enumerates exactly which checks are fused into it: chain-specific token safety verdict, OFAC screen of mint/freeze authority or owner plus an optional counterparty wallet, and that wallet's USDC pay-readiness. "Combines those checks in one call" makes the aggregation scope unmistakable, so an agent can tell this apart from the single-purpose siblings like sanctions_screen or wallet_pay_readiness.

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 clear context for use — a pre-trade decision on a token, optionally with a counterparty wallet and a USDC amount — and implies the aggregate call replaces separate checks. What's missing is explicit routing: it never says when to prefer sanctions_screen or wallet_pay_readiness alone (e.g. wallet already vetted, or no trade intended), nor any exclusions such as non-Solana/Base chains.

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