Skip to main content
Glama

apis-io

by io.apis
OverviewDiscussionsAdmin

get_playground_apis

Read-only

Curated APIs that are SAFE TO EXPERIMENT WITH — no key (or an instant, free, self-serve key), no cost, and no real-world side effects. Free, and deliberately so: this is where you start if you are new here. Every entry carries an example_request URL that returned HTTP 200 to an unauthenticated GET on the date shown, so it can be called immediately with no setup. Use this when you are new to this catalog, learning what an API call feels like, testing a tool-use loop, or need a harmless endpoint to demonstrate something. Defaults to the starter set; pass grouping="deep-archive" for institutional/OAI-PMH repositories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter by subject tag, e.g. weather, books, energy.
limitNo
accessNono-key = callable right now; instant-key = free self-serve key.
contextNoOptional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.
groupingNostarter (default) is the good-first-experience set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+  "type": "string"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint, it discloses that calls need no key or only an instant free key, incur no cost or side effects, and that each entry's example_request URL returned HTTP 200 to an unauthenticated GET as of the shown date. It also states the default grouping, so the agent knows what to expect without invoking the tool.

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?

The description is front-loaded with the core safety/value proposition, followed by concrete usage scenarios and the key parameter default. Every sentence earns its place and there is no filler, even though it is richer than a minimal definition.

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?

With no output schema, it still tells the agent what to expect from entries (each carries an example_request URL) and how to adjust grouping for different repository types. Optional parameters are covered by the schema or description, and the read-only, no-side-effect behavior is fully disclosed.

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 schema covers most parameters, but the description adds meaning by defining grouping: starter is the default and deep-archive is for institutional/OAI-PMH repositories. It also ties the access semantics to the no-setup promise, reinforcing the parameter's practical significance beyond the enum descriptions.

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 names a specific resource ('curated APIs') and the exact purpose: safe, no-cost, no-side-effect experiments for newcomers. It clearly distinguishes this from the many find_/get_ siblings by framing it as the 'start here' playground rather than a general API search.

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 explicitly says when to use it: when new to the catalog, learning what an API call feels like, testing a tool-use loop, or needing a harmless endpoint for demonstration. It doesn't name a specific alternative or negative condition, but the context is clear enough for an agent to avoid using this for general API discovery.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All apis-io toolsInspect
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