Skip to main content
Glama

Start here: BlazarForce overview

blazar_overview
Read-onlyIdempotent

START HERE. One call that returns what is live on BlazarForce 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.

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

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is not the description's burden. The description still adds value annotations cannot: it discloses that the payload reflects live state ("right now"), includes operational facts like the 5 bps wrapper / 30 bps pool fees, and warns that reward status can be a sentinel value such as REWARDS_ENDED with a date. It does not mention latency, caching, or payload 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?

The imperative "START HERE" is front-loaded and the single enumerative sentence maps each clause to content the caller receives, so nothing is decorative. The inline fee figures (5 bps, 30 bps) are the least essential fragment, but they preview data the agent would otherwise have to call twice to learn.

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?

There is no output schema, so the description carries the return-value burden and does so by itemizing what comes back and even showing the shape of one status field. For a parameterless read-only overview tool with annotations covering the safety profile, an agent has everything needed to decide to call it and interpret the response.

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 and the schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter explanation is required or missing.

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?

"One call that returns what is live on BlazarForce right now" names both the verb and the resource, then enumerates the concrete contents (contract addresses, fees, pools, BZB prices per venue, reward status). It also positions itself against the sibling catalog by promising "which tool to use for what", so an agent can distinguish it from blazar_pools, blazar_prices, or blazar_contracts without opening any schema.

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?

"Use it first in a session, or when unsure which tool fits" gives an explicit trigger condition plus a fallback rule that resolves exactly the ambiguity a 29-tool sibling set creates. It states no exclusions, but for a zero-parameter read-only entry-point tool the positive guidance is sufficient to route an agent correctly.

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