Skip to main content
Glama

FreeAPI.watch

Search free public APIs by need

search_free_apis

Finds free public APIs matching a topic, ranked by measured uptime. Filter to only those needing no API key, or only those above an uptime threshold. Use this when you need an API for a task and want one that currently works.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return. Default 10, max 50.
queryNoWhat you need, e.g. 'weather forecast', 'movie metadata', 'currency exchange'. Optional if category is given.
categoryNoRestrict to one category. Call list_categories for valid values.
min_uptimeNoMinimum 30-day uptime percentage, 0-100. Default 0.
no_auth_onlyNoOnly return APIs that need no API key or signup. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 usefully discloses that results are ordered by measured uptime and that filters are optional, but says nothing about what a result contains, pagination, or what happens when uptime data is missing for an API.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with the capability statement front-loaded and filters and usage conditions following in priority order. 'want one that currently works' borders on restating 'ranked by measured uptime' but reinforces the value proposition rather than wasting the sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five optional parameters, no annotations, and no output schema, the description should describe the shape of a returned API entry and confirm that query/category are alternatives. It conveys enough to invoke the tool but leaves the agent guessing about results and about what happens when neither query nor category is supplied.

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?

Schema coverage is 100%, so baseline is 3, and the description adds real meaning on top: it identifies the ranking signal behind min_uptime, frames query as a topical need, and clarifies no_auth_only as excluding signup as well as keys. The interplay of limit and ranking order is left unstated.

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?

States a specific verb and resource ('Finds free public APIs') plus the distinguishing ranking criterion ('ranked by measured uptime'). It does not name a sibling such as find_alternatives or list_dead_apis, so the differentiation from alternatives must be inferred rather than read.

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?

Gives a clear triggering condition ('Use this when you need an API for a task and want one that currently works') and explains when to apply the two filters. It stops short of stating when NOT to use it or explicitly deferring to check_api_status / find_alternatives.

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