Skip to main content
Glama

Blazar Polygon plugin

Ways to earn with BZB / POL (live reads)

blazar_earn_strategies
Read-onlyIdempotent

Earning options on BlazarForce ranked from live onchain reads only (no projections): BZB staking, BlazarSwap LP positions with reserves, trading rewards, and the BZB cross-venue spread. alerts[] at the top flags ended rewards and thin liquidity. Use when the user asks how to earn with BZB or POL here. 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_earn_strategies"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeVolumeNoAdd 24h swap volume per BlazarSwap pool from Swap events (slower, ~5 s).

Output Schema

NameRequiredDescriptionDefault
asOfNo
noteNo
alertsNo
pricesNo
chainIdNo
strategiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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), and the description adds meaningful context beyond them: results come from live onchain reads with no projections, alerts[] surfaces ended rewards and thin liquidity, and scope is restricted to Polygon (chain 137). It does not explain ordering or rate/latency behavior beyond the schema's own note.

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?

Two compact sentences, front-loaded with the tool's content rather than the name, with the usage clause and chain constraint trailing. Dense jargon ('reserves', 'cross-venue spread', 'alerts[]') is a minor readability cost but every sentence carries information.

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 read-only aggregation tool with an output schema, the description supplies what the schema cannot: data provenance (live reads, no projections), freshness caveats via alerts[], and chain restriction. What 'ranked' means in ordering is left implicit, and no alternative tools are pointed to.

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?

There is a single optional parameter with 100% schema description coverage, and the schema already explains includeVolume and its cost (~5 s). The description adds no further parameter meaning, so the baseline 3 applies.

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 with enumerated contents: BZB staking, BlazarSwap LP positions, trading rewards, and the BZB cross-venue spread, all from live reads. An agent can tell this is an earning-options discovery tool rather than a quote, build, or rank tool. It stops short of naming a sibling it is not, so 4 rather than 5.

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?

Gives explicit when-to-use guidance: 'Use when the user asks how to earn with BZB or POL here.' No when-not-to-use conditions and no named alternatives (e.g., blazar_rank_earning or blazar_pools) are given, so it is clear context without exclusions.

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