Skip to main content
Glama

Blazar Polygon plugin

Recent swaps / pool events (log polling)

blazar_recent_events
Read-onlyIdempotent

Read recent onchain events by log polling: BlazarFeeRouter AggregatedSwap (trader, tokens, amounts, USD) or one BlazarSwap pair's Swap + Sync (reserves and price). Returns nextFromBlock to poll again. Up to 5,000 blocks per call (about 2 hours). Polygon only (chain 137).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>"
    },
    "name": "blazar_recent_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairNoBlazarSwap pair address (source=pair). From blazar_pools.
blocksNoBlocks to scan, max 5000. Default 900 (~30 min).
sourceYesfeeRouter: AggregatedSwap events. pair: Swap + Sync on one BlazarSwap pair.
fromBlockNoStart block (use nextFromBlock from the last call). Default: head - blocks + 1.

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
eventsNo
sourceNo
toBlockNo
fromBlockNo
nextFromBlockNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so safety is covered. The description adds real behavioral context beyond that: the mechanism is log polling, the hard cap is 5,000 blocks (~2 hours) per call, execution is Polygon-only (chain 137), and the response carries nextFromBlock. It does not discuss error behavior for out-of-range or pruned fromBlock values.

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 compact sentences with no filler, led by the verb and mechanism, then the two source variants, then the two operational constraints (block cap, chain restriction). Every sentence carries constraint 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 an output schema present, the description need not explain return shapes, and it still usefully flags nextFromBlock for continued polling. Chain restriction and per-call block limits are the key constraints and both are stated. Minor gaps remain around behavior at the edges of the block range, but nothing essential is missing for a correct first call.

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?

Schema description coverage is 100%, so the schema already documents source, pair, blocks and fromBlock including defaults and the 5,000 maximum. The description restates the mode semantics (feeRouter events vs pair Swap+Sync) at a level the enum already conveys, adding little new syntax or format detail. Baseline 3 is appropriate.

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?

The description uses a specific verb plus resource ('Read recent onchain events by log polling') and names both source modes precisely: BlazarFeeRouter AggregatedSwap versus a BlazarSwap pair's Swap + Sync. An agent immediately knows what data comes back. It stops short of naming a sibling tool it should be preferred over, so it is clear but not sibling-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the polling story and the mention of returning nextFromBlock to poll again, which gives a concrete follow-up loop. However, there is no explicit when-to-use versus when-not guidance, and no alternative tool named for cases like historical lookups or decoding a known tx (e.g. blazar_decode_tx).

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