Skip to main content
Glama

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.

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

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: this is a static reference list scoped to Polygon, and it enumerates the contract categories returned. It stops short of describing the exact return shape or ABI link format.

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, both front-loaded: the returned contents come first, then the usage rule and sibling pointer. Nothing is padding, and each sentence carries distinct 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?

With no output schema and no parameters, the description carries the burden of describing the return value, and enumerating the contract categories largely does that. A brief note on the response structure (e.g., how the ABI links are formatted) would make it fully complete.

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 and the baseline of 4 applies. The mention of 'ABI link' is descriptive of returned content rather than a call-time option, which is harmless.

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 the specific resource set (router, factory, fee router, staking, daily rewards, oracle, BZB addresses plus the pair init code hash) on Polygon, so an agent knows exactly what comes back. It also distinguishes itself from the sibling blazar_overview, which 'already includes these.'

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 trigger condition explicitly ('Use when you need an address or ABI link') and flags the redundancy case by noting blazar_overview already includes the same data. That is both a when-to-use and an implicit when-not-to-use, tied to a named sibling.

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