EOL Watch

List services

list_services

Read-only

Lists every service that has a published item, with its number of items, how many of them are upcoming and the date of the next one. Use it to find the slug of a service before you filter search_items by service, or to see what is tracked for one cloud.

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

Input Schema

Name	Required	Description	Default
`q`	No	Search text of at most 100 characters. Every word must occur in the name or the slug of the service.
`cloud`	No	Only the services of this cloud.

Output Schema

Name	Required	Description
`site`	Yes	The site the data comes from.
`as_of`	Yes	The UTC day (YYYY-MM-DD) every value that depends on the day was counted for.
`count`	Yes	Number of services in this answer.
`license`	Yes	The license of the data.
`services`	Yes	The services, by cloud and then by name.
`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.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds the non-obvious scoping rule that services without published items are excluded. It also previews the aggregate fields returned, though an output schema exists so that is bonus rather than required.

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: the first defines output content, the second defines when to call it. No redundant restatement of the title and no filler.

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?

Annotations cover safety, the schema covers both parameters, and an output schema covers return shape. The description fills the remaining gap (that only services with published items appear, and that this is the slug-resolution step before search_items) without needing to repeat structured data.

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%, so both q and cloud are fully documented in structured data. The description only lightly gestures at the cloud filter via 'what is tracked for one cloud' and says nothing about the q search behavior, so it adds little beyond the schema — baseline 3 applies.

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 (lists) and resource (services), and goes further by defining the scope — only services that have a published item — plus the per-service payload (item count, upcoming count, next date). This distinguishes it clearly from search_items, which is named explicitly.

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 concrete when-to-use cases: resolving a service slug before filtering search_items by service, and inspecting what is tracked for a single cloud. The alternative tool is named along with the condition that selects it.

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?