Skip to main content
Glama

Token list

blazar_tokens
Read-onlyIdempotent

Uniswap-schema token list (BZB, BBY, WPOL, USDC, USDT, WETH, WBTC, M421) with addresses, decimals and transfer-tax flags. Use to resolve a symbol to an address.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "blazar_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond that: the dataset is a fixed enumerated set of eight tokens and each entry carries addresses, decimals and transfer-tax flags — transfer-tax flags being a behavioral trait of the tokens an agent could otherwise miss. It does not mention freshness/staleness or whether the list is chain-scoped, which keeps it at 4.

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?

Two sentences, no filler. Contents and fields come first, the intended use case last, so the agent can stop reading as soon as it knows this is the symbol-to-address source.

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?

With no input parameters and no output schema, the description carries the burden of describing the return shape, and it does so by naming the per-entry fields (addresses, decimals, transfer-tax flags). The one real gap is chain/network scope — the tickers (WPOL, M421) hint at a specific chain but nothing states it — so an agent cannot confirm from the definition alone which network these addresses apply to.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description correctly presents it as a no-argument lookup rather than implying filtering options that do not exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (a Uniswap-schema token list) and enumerates its contents and fields, then names the primary operation: resolving a symbol to an address. That is far beyond a restatement of the name/title. It stops short of 5 because it does not contrast itself with nearby siblings such as blazar_contracts or blazar_prices, so the agent must infer that this is the lookup source rather than a price or contract-metadata source.

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?

"Use to resolve a symbol to an address" gives an explicit, actionable when-to-use condition and is the most common entry point in this toolset. There is no statement of when not to use it or of which sibling to pick for price or contract-ABI data, so the guidance is clear but not complete.

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