Skip to main content
Glama

FreeAPI.watch

Find working alternatives to an API

find_alternatives

Given an API that is dead, paywalled, rate-limiting you, or simply unsuitable, returns free alternatives in the same category ranked by measured uptime. Use this when an integration breaks or an API goes paid.

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

Input Schema

NameRequiredDescriptionDefault
apiYesThe API you are replacing, by slug or name, e.g. 'dark-sky', 'twitter'.
limitNoMaximum alternatives to return. Default 5, max 20.

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?

No annotations are supplied, so the description carries the full behavioral burden. It discloses the important traits that results are free-only, category-matched, and ordered by measured uptime, but says nothing about behavior when no alternatives exist (empty result vs. error) or whether the call is a pure read with no side effects.

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 tight sentences with zero filler: the trigger conditions and output shape come first, and the invocation cue follows. Nothing could be removed without losing information.

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 two-parameter read tool with no output schema, the description covers triggers, output nature, and ranking sufficiently. The only meaningful omission is empty-result/error behavior, which is a modest gap rather than a blocking one.

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%, with both 'api' and 'limit' documented including examples, defaults, and maximum. The description adds no meaning beyond that, so the baseline of 3 applies.

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 free alternatives') along with the scope ('in the same category') and ranking rule ('by measured uptime'), which is far more than a restatement of the name. It does not explicitly distinguish itself from the sibling 'search_free_apis', leaving the boundary between lookup-by-known-API and open search to inference.

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 this when an integration breaks or an API goes paid' plus the enumerated triggers (dead, paywalled, rate-limiting, unsuitable) gives clear positive when-to-use guidance. There are no exclusions or named alternatives for the opposite case (e.g., browsing a catalog when you don't yet have an API to replace).

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