pons-mcp

pons_recent_graduations

Retrieve recent PoolGraduated events newest-first, including token, positionId, swept token/pair amounts, block, and tx hash. Find factory graduations within a lookback window.

Instructions

Scan factory PoolGraduated events newest-first: token, positionId, swept token/pair amounts, block, tx hash.

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": "pons_recent_graduations"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max results, newest first (default 20, max 100)
`lookbackBlocks`	No	Blocks to look back from latest (default 50000 ≈ 1.4h at ~10 blocks/s; max 500000)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 15, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses ordering ('newest-first'), the event source, and output fields, but does not explicitly state that this is a read-only operation, clarify what 'swept token/pair amounts' precisely means, or mention behavior such as empty results or block-range edge cases. Acceptable but not rich.

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?

One dense sentence with no filler. The action, ordering, and output fields are front-loaded, and every phrase earns its place. This is an ideal length for a simple event-scanning tool.

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?

For a straightforward read-only scanner with 100% schema coverage, the description is largely complete: it lists the returned fields, which matters because there is no output schema. It could add a touch more context about the factory contract or result shape, but nothing essential is missing for invocation.

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 baseline is 3 even though the tool description adds no parameter-level detail. The schema fully documents 'limit' and 'lookbackBlocks', including defaults, ranges, and units, so the description does not need to compensate.

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 verb ('Scan'), a concrete resource ('factory PoolGraduated events'), an explicit ordering ('newest-first'), and the exact returned fields. This clearly differentiates it from siblings like pons_recent_launches and pons_creator_launches without needing to inspect the schema.

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 context is implied rather than stated: an agent can infer 'use this when needing recent PoolGraduated events' from the description. However, there is no explicit when-to-use versus alternatives, no mention of exclusions, and no guidance about which sibling to choose for other graduation-related queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.