Skip to main content
Glama
Sign In

Solana Pulse: agent safety layer

by io.github.Timothymycompc
OverviewDiscussionsAdmin

find_token

Read-onlyIdempotent

Run whenever a user names a token ("buy BONK"). Tickers aren't unique; copycats reuse them. Never take an address from memory. Finds the real address for a ticker or name, ranks matches by verification and liquidity, and warns when copycats share the ticker. Example: {"name": "BONK"}. Cost: 25 free calls a day, then $0.01 USDC per call (x402). Outputs explained: GET /api/tools/find_token.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTicker, name or address: "BONK", "Jupiter", "USDC". Exactly as the user wrote it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The token's ticker, name or address, e.g. \"BONK\", \"Jupiter\", \"USDC\". The token name exactly as the user wrote it."New value: +"Ticker, name or address: \"BONK\", \"Jupiter\", \"USDC\". Exactly as the user wrote it."
  2. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"The token's ticker, name or address, e.g. \"BONK\", \"Jupiter\", \"USDC\". The token name exactly as the user wrote it."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior the annotations cannot convey: ranked-by-verification-and-liquidity results, copycat warnings, the x402 cost model with 25 free calls/day then $0.01 USDC per call, and a pointer to the output documentation. Rate/cost disclosure is exactly the kind of context annotations miss.

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 trigger condition and packs cost, ranking, and warning behavior into a short block. The trailing 'Outputs explained: GET /api/tools/find_token' is a slightly awkward fragment, and the embedded JSON example is marginally redundant, but overall no wasted sentences.

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 one-parameter, read-only lookup with no output schema, the description covers trigger, parameters, ranking semantics, edge cases (copycats), cost, and even points to where outputs are documented. Nothing material is missing for correct invocation.

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 schema already documents the 'name' parameter thoroughly, including the 'exactly as the user wrote it' guidance. The inline example {"name": "BONK"} restates what the schema already shows rather than adding new semantics, so the baseline 3 is appropriate.

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 verb and resource ('finds the real address for a ticker or name'), plus the ranking behavior and copycat warning. This is clearly distinguishable from siblings like token_safety, tokens, and balance, which an agent can tell apart without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger ('Run whenever a user names a token'), an explicit anti-pattern ('Never take an address from memory'), and the reason copycats make this necessary. The agent knows exactly when to reach for this tool and why shortcuts are dangerous.

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

All Solana Pulse: agent safety layer 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