Skip to main content
Glama

Blazar Polygon plugin

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. Polygon only (chain 137).

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

Output Schema

NameRequiredDescriptionDefault
nameNo
tagsNo
tokensNo
logoURINo
versionNo
keywordsNo
timestampNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description is not obligated to restate safety. It still adds meaningful behavior: the list is a fixed enumerable set of eight tokens, includes transfer-tax flags, and is restricted to chain 137 — telling the agent both what it gets and the boundary of coverage.

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 tight sentences, front-loaded with what the list is and its contents, then the use case and the chain constraint. Every clause carries information; nothing is redundant.

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?

An output schema exists, so return-field shape need not be re-explained, and the description still names the key fields (addresses, decimals, transfer-tax flags). The only minor gap is that it does not confirm whether the list is exhaustive or whether addresses are checksummed, but for a zero-parameter static lookup this is nearly complete.

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 (100% schema coverage), so there is no parameter meaning to add and the baseline of 4 applies. The description does not need to explain inputs because there are none.

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 resource (a Uniswap-schema token list) and enumerates exactly which tokens it contains (BZB, BBY, WPOL, USDC, USDT, WETH, WBTC, M421), plus the fields returned. This clearly separates it from siblings like blazar_token_safety (safety checks) and blazar_prices (price data).

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 trigger condition, and the "Polygon only (chain 137)" line tells the agent when the tool does not apply. It stops short of naming an alternative for non-Polygon chains or for safety lookups, so it is not a full when/when-not routing statement.

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