AnyAPI

Browse APIs

list_apis

Read-only

Browse available AnyAPI APIs as lightweight summaries (id, name, category, USD pricing) - no descriptions or schemas, so it stays cheap even across the whole catalog. Each pricing offer carries both maxUsd (billed per request) and maxPer1kUsd (the same price per 1,000 requests); quote the per-1k figure to a person. Optionally filter by category. Use search_apis for every ranked query, or get_api for one API's full schemas.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
`category`	No	optional category slug to filter by

Output Schema

TableJSON Schema

Name	Required	Description	Default
`scrapers`	Yes	matching APIs (lightweight summaries: no description or schemas)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 14, 2026

addedOutput schema / properties / scrapers / items / properties / pricing / properties / from / properties / addons

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "field": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "usd": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "id",
+      "label",
+      "field",
+      "usd"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

Changed17 schema fields changedSep 3, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}

removedInput schema / properties / query

Removed value: -{
-  "description": "optional free-text filter over API name and description",
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "context"
+]
```

removedOutput schema / properties / scrapers / items / properties / baseUsd

Removed value: -{
-  "description": "fixed cost per request in USD, charged regardless of count",
-  "type": "number"
-}

addedOutput schema / properties / scrapers / items / properties / excludesCallerDelay
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / scrapers / items / properties / execution

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "mode": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "mode"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / scrapers / items / properties / failover
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / scrapers / items / properties / heavy / description

Removed value: -"true when this API's responses are typically large; pass fields, max_items, or summary to run_api (and a small limit in the input) to keep the result out of your context"

addedOutput schema / properties / scrapers / items / properties / method
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / scrapers / items / properties / path
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / scrapers / items / properties / perItemUnit

Removed value: -{
-  "description": "the unit perItemUsd is charged per: 'result' (default) or an input unit like 'username' for input-priced SKUs",
-  "type": "string"
-}

removedOutput schema / properties / scrapers / items / properties / perItemUsd

Removed value: -{
-  "description": "marginal cost in USD per billable unit (see perItemUnit); total = baseUsd + perItemUsd × unitCount, capped at priceUsd",
-  "type": "number"
-}

removedOutput schema / properties / scrapers / items / properties / priceUsd

Removed value: -{
-  "description": "maximum price per request in USD (the reserved ceiling at the default limit)",
-  "type": "number"
-}

addedOutput schema / properties / scrapers / items / properties / pricing

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "failoverMaxPer1kUsd": {
+      "type": "number"
+    },
+    "failoverMaxUsd": {
+      "type": "number"
+    },
+    "from": {
+      "additionalProperties": false,
+      "properties": {
+        "baseUsd": {
+          "type": [
+            "null",
+            "number"
+          ]
+        },
+        "maxPer1kUsd": {
+          "type": "number"
+        },
+        "maxUsd": {
+          "type": "number"
+        },
+        "model": {
+          "type": "string"
+        },
+        "perUnitUsd": {
+          "type": [
+            "null",
+            "number"
+          ]
+        },
+        "unit": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "model",
+        "unit",
+        "maxUsd",
+        "maxPer1kUsd"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "from",
+    "failoverMaxUsd",
+    "failoverMaxPer1kUsd"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / scrapers / items / properties / provider
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / scrapers / items / required

Previous value: -[
-  "id",
-  "slug",
-  "category",
-  "name",
-  "priceUsd",
-  "baseUsd",
-  "perItemUsd"
-]New value: +[
+  "id",
+  "slug",
+  "category",
+  "name",
+  "method",
+  "path",
+  "provider",
+  "execution",
+  "pricing",
+  "failover"
+]

Changed1 schema field changedJul 10, 2026

addedOutput schema / properties / scrapers / items / properties / heavy

Added value: +{
+  "description": "true when this API's responses are typically large; pass fields, max_items, or summary to run_api (and a small limit in the input) to keep the result out of your context",
+  "type": "boolean"
+}

Changed5 schema fields changedJun 24, 2026

changedOutput schema / properties / scrapers / description

Previous value: -"matching APIs"New value: +"matching APIs (lightweight summaries: no description or schemas)"

removedOutput schema / properties / scrapers / items / properties / description
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / scrapers / items / properties / inputSchema
```
Removed value: -{
-  "description": "normalized input JSON Schema"
-}
```
removedOutput schema / properties / scrapers / items / properties / outputSchema
```
Removed value: -{
-  "description": "normalized output JSON Schema"
-}
```

changedOutput schema / properties / scrapers / items / required

Previous value: -[
-  "id",
-  "slug",
-  "category",
-  "name",
-  "description",
-  "priceUsd",
-  "baseUsd",
-  "perItemUsd"
-]New value: +[
+  "id",
+  "slug",
+  "category",
+  "name",
+  "priceUsd",
+  "baseUsd",
+  "perItemUsd"
+]

First observedJun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: cost characteristics ('stays cheap even across the whole catalog') and pricing unit semantics (maxUsd vs maxPer1kUsd). It does not contradict annotations and provides useful non-obvious details about output interpretation.

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 compact and front-loaded with the core purpose in the first sentence. Each subsequent sentence adds distinct value (cost trade-off, pricing detail, routing). No filler or repetition; appropriate length for the complexity of the tool.

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

Completeness5/5

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

Given that an output schema is present (no return-value elaboration needed), the description covers all essential agent-facing information: what the tool returns (summaries), its limitations (no descriptions/schemas), pricing guidance, the optional filter, and sibling tool selection. Nothing an agent needs to decide or call correctly is missing.

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% for both parameters (context and category). The description only restates the category filter ('Optionally filter by category') which is already documented in the schema. It adds no new meaning about parameter syntax or values beyond what the schema provides, so it meets the baseline without exceeding it.

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 starts with a clear verb-resource pair ('Browse available AnyAPI APIs') and specifies the exact content ('lightweight summaries (id, name, category, USD pricing)'). It also explicitly names sibling tools ('search_apis', 'get_api') and states what this tool is NOT (no descriptions or schemas), fully distinguishing it from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit routing: 'Use search_apis for every ranked query, or get_api for one API's full schemas.' It also notes the optional category filter and the intended use case (cheap whole-catalog browsing). This gives clear when-to-use and when-not-to-use guidance without ambiguity.

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

All AnyAPI tools Inspect

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.