Skip to main content
Glama

FreeAPI.watch

List APIs that died or went paid

list_dead_apis

Returns the graveyard: APIs that shut down or moved behind a paywall, with what replaced them. Use this to avoid generating code against an API that no longer exists — training data frequently still recommends these.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries to return. Default 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the returned content, including replacement APIs, but does not mention read-only safety, ordering, freshness, pagination, or authentication expectations.

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 the return content and followed by a concrete usage warning. The wording is efficient and avoids repeating the title or schema.

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 simple read-only listing tool with one optional parameter, the description is nearly sufficient: it explains what is returned and why to call it. A little more detail about result structure or sibling routing would make it complete.

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?

The only parameter is fully documented in the schema, including its default of 25. The description does not add any additional meaning about the limit parameter, so the schema baseline 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?

The description states a specific resource and scope: APIs that shut down or moved behind a paywall, including replacement information. This is more specific than the name alone and clearly distinguishes the tool from active/free API search or status-check siblings.

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 an explicit use case: avoid generating code against dead APIs because training data may still recommend them. It does not name alternatives such as check_api_status or find_alternatives, so it lacks the explicit routing guidance of a 5.

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