Skip to main content
Glama
Sign In
bonk-mcp

bonk-mcp

by Akhil0g
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

token-lookup

Retrieve a Solana token's mint address by entering its ticker symbol.

Instructions

Lookup token mint addresses by ticker symbol

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

Input Schema

NameRequiredDescriptionDefault
tickerYesToken ticker symbol (e.g., SOL, BONK, USDC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.10

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It states only the action 'lookup', which implies read-only, but does not confirm safety, mention edge cases, or describe what happens if the ticker is unknown.

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 description is a single concise sentence and front-loads the action, with no redundant words. However, its brevity leaves out useful context, making it efficient but perhaps too sparse.

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

Completeness3/5

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

For a one-parameter tool with no output schema and no annotations, the description gives the essential function but omits details about the return format, potential errors, and whether the operation is safe, leaving the agent to infer from the tool name and siblings.

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?

The schema already fully documents the 'ticker' parameter with examples; the description's 'by ticker symbol' adds no new semantic information beyond what the schema provides.

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 uses a specific verb 'Lookup' and identifies the resource as 'token mint addresses', clearly distinguishing it from sibling tools like buy-token or launch-token.

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

Usage Guidelines2/5

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

The description implies a use case (converting ticker to mint address) but does not explicitly state when to choose this tool over alternatives, nor any prerequisites or context.

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

Deploy Server

Other Tools