Skip to main content
Glama

BlazarSwap pools and reserves

blazar_pools
Read-onlyIdempotent

List every BlazarSwap V2 pair on Polygon with live reserves. Use for liquidity checks or LP decisions. For a trade price use blazar_quote instead (it also covers QuickSwap and Sushi).

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_pools"
  }
}

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, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are live on-chain reserves (not cached), and coverage is limited to V2 pairs on Polygon. It stops short of describing pagination or result size, hence 4 rather than 5.

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?

Three short sentences, zero filler, with the core action front-loaded and the sibling routing pushed to the end where it belongs. Every clause carries information an agent needs.

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 parameters, rich annotations, and no output schema, the description covers the essentials: what is returned (pairs with live reserves), the chain and protocol scope, and the correct sibling for pricing. A brief note on the per-pair fields (token addresses, fee tier) would close the remaining gap.

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 beyond the schema's empty object. The description correctly frames the implicit filtering (chain = Polygon, protocol = BlazarSwap V2) that substitutes for parameters.

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?

States a specific verb and resource ('List every BlazarSwap V2 pair on Polygon') plus a data-quality qualifier ('with live reserves'). The scope restrictions (V2 only, Polygon only, BlazarSwap only) make it immediately distinguishable from the broader-priced sibling blazar_quote.

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?

Gives two positive use cases ('liquidity checks or LP decisions') and an explicit exclusion with a named alternative: 'For a trade price use blazar_quote instead (it also covers QuickSwap and Sushi).' The condition that selects the sibling is spelled out, not inferred.

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