Skip to main content
Glama

FreeAPI.watch

Check whether an API is up right now

check_api_status

Returns the live status of a tracked free API: whether the last hourly check succeeded, the measured response time, 30-day uptime, the free-tier terms, and whether an API key is required. Use this before writing code against an API to confirm it is actually alive and still free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "api": "<api>"
    },
    "name": "check_api_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiYesAPI slug or name, e.g. 'open-meteo', 'TMDB', 'pokeapi'. Matching is fuzzy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose useful behavioral context beyond a bare read: checks run hourly, results are 'live', and the response includes uptime windows and key requirements. However, it says nothing about what happens when the slug is unknown, whether untracked APIs can be looked up, or any rate limits, which are the gaps an agent would hit at invocation time.

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, both earning their place: the first front-loads what is returned, the second front-loads when to call it. No filler, no restatement of the title, and the enumeration of returned signals is compact.

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?

There is no output schema, so the description must describe return values and it does so item by item, which is the main completeness requirement for this tool. The remaining gap is failure behavior for an untracked or misspelled slug, which matters given fuzzy matching but goes unmentioned.

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% and the single parameter is fully documented in the schema, including the fuzzy-matching behavior and example slugs. The description adds no parameter-level meaning, so the baseline of 3 applies even though nothing is missing.

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 opens with a specific verb and resource ('Returns the live status of a tracked free API') and enumerates exactly which signals come back (last hourly check result, response time, 30-day uptime, free-tier terms, key requirement). That is far more precise than the title alone. It stops short of naming a sibling such as list_dead_apis to draw the contrast explicitly, so differentiation is inferable rather than stated.

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?

The second sentence gives a concrete trigger: 'Use this before writing code against an API to confirm it is actually alive and still free.' That is a clear usage context an agent can act on. There is no stated exclusion or named alternative for the case where the agent wants to discover APIs it hasn't chosen yet, which is what keeps this below 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