EOL Watch

List providers, tools and modules

list_providers

Read-only

Lists the infrastructure as code providers, tools and modules whose releases are read for breaking changes, each with its newest tracked release. Use it to find the key that get_provider_changes takes.

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_providers"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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 entries in this answer.
`license`	Yes	The license of the data.
`providers`	Yes	The providers and tools, then the modules, in the order of the site.
`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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds behavior beyond that by disclosing the return shape (each provider comes with its newest tracked release) and framing the tool as a key-lookup index. It does not discuss volume, pagination, or refresh behavior, but with zero parameters and an output schema those are minor gaps.

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, zero waste: the first establishes what is listed and what each entry includes, and the second immediately routes the agent to the consuming tool. The purpose is front-loaded ahead of the usage instruction.

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 zero-parameter, read-only discovery tool with an output schema, the description covers everything an agent needs: what is returned, why it matters, and which sibling call to make next. Return-value detail beyond the provided output schema is not required, yet the description still summarizes it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description's note that it returns the “key” used by get_provider_changes implicitly explains the one identifier an agent needs to carry forward, which is mild added value.

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 pairs a specific verb ("Lists") with a clearly bounded resource ("infrastructure as code providers, tools and modules whose releases are read for breaking changes") and adds the scope detail that each entry carries its newest tracked release. It also names the sibling get_provider_changes and states how the two relate, so an agent can tell them apart without opening either schema.

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?

It gives concrete when-to-use guidance: "Use it to find the key that get_provider_changes takes," which ties this discovery tool to the exact downstream call that consumes its result. There is no explicit when-not-to-use or mention of the other sibling tools, keeping it just short of a 5.

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?