Skip to main content
Glama

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.

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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real value by stating values are live reads rather than projections and that alerts[] is surfaced at the top to flag ended rewards and thin liquidity. It does not describe latency, rate limits, or what happens when no strategies are found.

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 sentences, front-loaded with scope ('live onchain reads only') before the enumeration, and zero filler. The list of categories is dense jargon (reserves, cross-venue spread) but each phrase carries information. Slight compression cost, not bloat.

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 output schema, the description does the work of explaining what surfaces (per-strategy categories plus a top-level alerts[] with two flag types), which is the key structural fact an agent needs. Missing detail on the per-strategy fields and behavior on empty results keeps it from a 5, but it is adequate for a read-only, parameter-light tool.

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 one optional parameter with full schema description coverage, including the ~5s cost of includeVolume. The description adds nothing beyond the schema about that flag. Baseline 3 applies when the schema already does the work.

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 concrete resource (earning options on BlazarForce) and scopes it: live onchain reads only, no projections. It enumerates the categories covered (BZB staking, BlazarSwap LP with reserves, trading rewards, cross-venue spread), which tells an agent exactly what comes back. It does not explicitly differentiate itself from nearby siblings such as blazar_rank_earning or blazar_daily_rewards, so it stops short of 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 an explicit trigger: 'Use when the user asks how to earn with BZB or POL here.' That is a clear use context. It offers no exclusions or named alternatives for cases like 'how much have I earned' or 'rank the best yield', which leaves some routing inference to the agent.

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