Skip to main content
Glama
Sign In
obol

obol

by halfkey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

obol_token_metadata

Retrieve token metadata including name, symbol, supply, and decimals for any Solana mint address. Pay $0.01 USDC per request.

Instructions

Get token metadata — name, symbol, supply, decimals. Costs $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault
mintYesToken mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose a cost of $0.01 USDC, which is a meaningful operational detail, but it does not explicitly state read-only nature or other constraints. This is partial but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence that front-loads the purpose and includes the cost. There is no redundant wording, making it concise and efficient.

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?

The tool is simple with one parameter and no output schema. The description lists the returned fields and cost, which is sufficient for an agent to initiate a call. While error handling is not mentioned, the simplicity of the tool makes the description adequately complete.

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 input schema fully describes the mint parameter as 'Token mint address' (100% coverage), and the description adds no additional meaning or format details. The baseline of 3 applies because the schema already handles parameter 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?

The description clearly states the tool's function: 'Get token metadata' and explicitly lists the returned fields (name, symbol, supply, decimals). This is a specific verb-resource combination that distinguishes it from sibling tools like token price.

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?

No guidance is provided on when to use this tool versus alternative obol tools. The description does not mention exclusions, alternatives, or typical scenarios, leaving the agent to infer usage solely from the tool name.

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