Skip to main content
Glama

Blazar Polygon plugin

Contract addresses

blazar_contracts
Read-onlyIdempotent

BlazarForce contract addresses on Polygon (router, factory, fee router, staking, daily rewards, oracle, BZB) plus the pair init code hash. Use when you need an address or ABI link; blazar_overview already includes these. 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_contracts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
abisNo
feesNo
chainIdNo
contractsNo
initCodePairHashNo

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=false, so the safety profile is covered. The description adds useful context beyond that: the data is a fixed set of named contract addresses plus an init code hash, and it is Polygon/chain-137 specific. It does not say whether addresses are versioned or could change, which is the only remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the resource and its contents, then the usage/scope constraint. Every clause carries information: the enumerated address set, the sibling comparison, and the chain restriction.

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 an output schema present, the description need not explain return values, and it still enumerates the address categories and the chain constraint. The only loose end is the mention of an 'ABI link' that is not part of the enumerated contents, leaving slight ambiguity about whether ABIs are actually returned.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its words on what the parameterless response contains, which is the right use of space.

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 names a specific resource (BlazarForce contract addresses) and enumerates exactly what is returned: router, factory, fee router, staking, daily rewards, oracle, BZB, plus the pair init code hash. It also explicitly distinguishes itself from the sibling blazar_overview, so an agent can choose between them without opening a 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?

It states the triggering condition ('Use when you need an address or ABI link') and names the alternative that already carries the same data ('blazar_overview already includes these'), which is real routing guidance. It also pins the scope with 'Polygon only (chain 137)', preventing a wrong-chain call.

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