Skip to main content
Glama

Blazar Polygon plugin

Start here: BlazarForce overview

blazar_overview
Read-onlyIdempotent

START HERE. One call that returns what is live on BlazarForce (Polygon) right now: contract addresses, fees (5 bps wrapper, 30 bps pool), top BlazarSwap pools, BZB price per venue, staking and trading-reward status (e.g. REWARDS_ENDED with date), and which tool to use for what. Use it first in a session, or when unsure which tool fits. For Base / Ethereum support see blazar_chains.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
feesNo
nameNo
toolsNo
unitsNo
chainsNo
safetyNo
statusNo
chainIdNo
networkNo
rewardsNo
bzbPriceNo
topPoolsNo
asOfBlockNo
contractsNo
whyUseThisNo
whenNotToUseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description is not obligated to restate it. It adds real context on what state is surfaced, including volatile items like live fee values and reward status strings such as REWARDS_ENDED with a date, which signals the response can shift between calls. It does not mention auth, rate limits, or response size, which keeps it short of a 5.

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?

Front-loaded with 'START HERE', then a compact enumeration of return contents followed by usage routing — the ordering matches how an agent decides to call it. The content list is long but each item serves routing value (fees, pools, price, reward status); minor trimming possible but nothing is clearly wasteful.

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

Completeness5/5

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

With zero params, a full output schema, and rich annotations, the only remaining burden is orientation and routing — both delivered. The description tells an agent what it will learn, when to reach for it first, and where to go for non-Polygon chains.

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; there are no parameter semantics for the description to clarify. The description correctly avoids inventing any input controls and instead spends its words on routing.

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-plus-resource framing ('One call that returns what is live on BlazarForce (Polygon) right now') and enumerates the concrete payload: contract addresses, fee tiers (5 bps wrapper, 30 bps pool), top pools, per-venue BZB price, and reward status. It also explicitly distinguishes itself from the sibling blazar_chains, which covers Base/Ethereum.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance ('Use it first in a session, or when unsure which tool fits') and names the boundary case with the correct alternative ('For Base / Ethereum support see blazar_chains'). Both the entry-point condition and the exclusion are stated, not implied.

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