Skip to main content
Glama

Blazar Polygon plugin

Supported chains: Polygon (primary), Base, Ethereum

blazar_chains
Read-onlyIdempotent

List supported chains: Polygon (137, primary: every tool, including BZB, BlazarSwap, staking, trading rewards and the fee router), Base (8453) and Ethereum (1) for the general tools only. Returns chain ids, native coin, wrapped native, USDC, explorer, public RPCs, curated tokens and which tools accept chain. Read-only, no network.

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_chains"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
chainsNo
primaryNo
howToUseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety bar is low. The description adds real context beyond that: 'no network', i.e. the data is static/embedded rather than fetched live, which tells the agent results are stable and cheap. There is a mild tension with openWorldHint=true, but 'no network' plausibly means no RPC calls rather than no external domain, so this is not treated as a contradiction.

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?

One front-loaded sentence leading with the action, then the per-chain breakdown, then the payload summary — a logical order with no filler sentences. The nested parenthetical listing every Polygon tool family is dense but earns its place by defining the primary-chain distinction. The title merely restates a fragment of the description, which is minor redundancy.

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 no-parameter, read-only lookup with an output schema, this is essentially complete: the agent knows the three chains, their ids, that Polygon is primary, and that Base/Ethereum are restricted to general tools. The enumerated return fields partially duplicate the output schema, and it does not state whether the chain list can grow, but neither gap would cause a mis-call.

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?

With zero parameters there is no parameter meaning to add, and the schema is fully covered, so the baseline of 4 applies. The description instead spends its words on the return payload (chain ids, native coin, wrapped native, USDC, explorer, RPCs, curated tokens, tool acceptance), which is useful orientation even if not strictly 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?

States a specific verb and resource ('List supported chains') and immediately enumerates exactly what comes back: Polygon 137, Base 8453, Ethereum 1. Crucially it distinguishes per-chain tool coverage (Polygon = every tool including BZB, BlazarSwap, staking, trading rewards, fee router; Base/Ethereum = general tools only), which is the distinguishing fact an agent needs and which no sibling name conveys.

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?

It gives clear context for interpreting capability differences across chains, implying an agent should consult this before assuming a chain-specific build tool works on Base or Ethereum. It stops short of explicit when-to-call/when-not guidance or naming which sibling to use instead when a chain lacks support (e.g. no pointer to blazar_contracts or blazar_overview).

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