Skip to main content
Glama
Sign In

SAID Protocol

by io.github.Jugmaster
OverviewDiscussionsAdmin

Check a token before you buy it

check_token
Read-onlyIdempotent

Two checks on a Solana token mint. (1) Authenticity: if it claims to be a tokenized stock or real-world asset, is it the issuer's real token or an impersonator, and is the backing verifiable? (2) Launch trust: who deployed it, how their previous launches ended, bundling and funding-trail flags, with a pass / caution / fail verdict. Every pass/fail verdict is re-graded at 24h and 7d on a public scoreboard. Free.

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

Input Schema

NameRequiredDescriptionDefault
mintYesToken mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. Beyond that, the description discloses output semantics the annotations cannot: a pass/caution/fail verdict, the specific flag categories, and the fact that verdicts are re-graded at 24h and 7d on a public scoreboard — meaningful context about how results should be interpreted.

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 two numbered checks, so the agent gets the essential structure immediately. The closing 'Free.' fragment and scoreboard sentence are arguably promotional, but they do carry trust-relevant information, so waste is minimal.

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 single-parameter read-only tool with no output schema, the description supplies enough about what comes back (authenticity determination, verdict, flag categories) to set expectations. Detail on result shape is not required since no output schema exists, though it remains unspecified.

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 single 'mint' parameter is fully documented with a base58 pattern. The description adds only the framing that it is a Solana mint, so there is no real semantic lift beyond the schema — 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 — 'Two checks on a Solana token mint' — and enumerates exactly what each check covers (issuer authenticity/backing verifiability, deployer history, bundling and funding-trail flags). That is clearly distinguishable from check_wallet and find_agent, which operate on different entities.

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

Usage Guidelines3/5

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

The 'before you buy it' framing and the 'free' note imply a pre-purchase due-diligence context, but the description never states when to choose this over check_wallet or find_agent, nor any when-not conditions. Usage is implied rather than prescribed.

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

All SAID Protocol 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