EOL Watch

List recent changes

recent_changes

Read-only

Returns one page of the changelog of EOL Watch, newest first: items added, effective dates changed, items updated and items withdrawn. Use it to see what changed since you last read the data.

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

Input Schema

Name	Required	Description
`page`	No	Page of the changelog, from 1. One page holds 50 changes, and a page past the end is the last page.
`cloud`	No	Only changes to items of this cloud.
`change`	No	Only this kind of change: added, date_changed, updated or withdrawn.

Output Schema

Name	Required	Description
`page`	Yes	The page this answer holds. A page past the end is the last page.
`site`	Yes	The site the data comes from.
`count`	Yes	Number of changes in this answer.
`items`	Yes	The changes of this page, newest first.
`pages`	Yes	Number of pages.
`query`	Yes	The query as it was understood.
`total`	Yes	Number of changes that match the query.
`license`	Yes	The license of the data.
`generated_at`	Yes	Moment this answer was built (ISO 8601, UTC).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds genuinely new behavioral context: results are ordered newest first and are paginated ('one page'). It does not discuss page-size or how to iterate, though the schema covers pagination details.

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, front-loaded with what is returned and why to use it, with zero filler. The enumerated change kinds directly map to the enum values an agent will need.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, filtered list tool with a complete output schema and fully described parameters, the description supplies everything needed: content, ordering, pagination, and the purpose of calling it. No critical gap remains.

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 page, cloud, and change. The description only restates the four change kinds that match the 'change' enum, adding no filtering semantics or defaults beyond the schema.

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 states a specific verb and resource ('Returns one page of the changelog of EOL Watch') and enumerates the change kinds returned, so an agent knows exactly what data it yields. It does not distinguish itself from the sibling get_provider_changes, leaving that differentiation to the agent.

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?

'Use it to see what changed since you last read the data' gives a clear triggering condition for the tool. There are no explicit exclusions or named alternatives (e.g., get_provider_changes), so it stops short of full routing guidance.

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

All EOL Watch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?