Skip to main content
Glama

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).

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so safety is covered. The description adds genuinely useful behavior beyond that: the 5,000-block (~2 hour) ceiling per call, the nextFromBlock cursor returned for continued polling, and the fields each event carries. It still omits error/partial-result behavior and rate limits, so a 3 fits rather than a 4.

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?

Front-loaded with the core action and mode split, and every clause carries information with no filler. The density of parenthetical field lists makes it slightly harder to scan than it needs to be, but nothing is wasted.

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?

There is no output schema, and the description compensates by naming the returned event fields and the nextFromBlock cursor. Given a four-parameter, single-required-parameter polling tool, an agent has enough to invoke it correctly, though pagination edge cases (no events, end-of-chain) go unaddressed.

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 coverage is 100% and every parameter already carries a description including defaults and the nextFromBlock convention, so the baseline is 3. The description's one value-add is interpreting the 5,000-block maximum as roughly two hours, which is marginal.

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?

States a specific verb and resource: 'Read recent onchain events by log polling,' then names the two concrete event sets (FeeRouter AggregatedSwap vs. a BlazarSwap pair's Swap + Sync) with the fields each yields. It does not distinguish itself from adjacent catalog tools such as blazar_prices or blazar_pools, which keeps it from a 5.

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

Usage Guidelines4/5

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

Explains the two operating modes via the source switch and describes the polling loop ('Returns nextFromBlock to poll again'), which is actionable context for repeated calls. It gives no explicit when-not-to-use guidance or pointer to a sibling tool for historical/aggregated queries.

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