RealWorldAPIs

Search APIs

search_apis

Read-onlyIdempotent

Search the canonical registry when you already know keywords or exact requirements. All supplied filter groups combine with AND logic; array capability filters require every supplied value, and protocol fields match the exact Yes/No/Unknown status, so Unknown never satisfies Yes. Results include each API's capability_summary and direct decision-profile URL. Results are sorted by agent_readiness_score descending and then API name, with 1–20 results returned (default 10). Use search_capabilities when you need capability-level filters such as approval, physical consequence, sandbox or access friction.

Input Schema

TableJSON Schema

Name	Required	Description
`a2a`	No	Exact A2A evidence status required for a match.
`mcp`	No	Exact MCP evidence status required for a match.
`x402`	No	Exact x402 evidence status required for a match.
`limit`	No	Maximum number of matching records returned. Results are sorted by readiness descending then API name. total_matches still reports the full count. No pagination is currently exposed.
`query`	No	Optional case-insensitive text search across API name, provider, category, description, capabilities, agent capabilities and authentication fields.
`openapi`	No	Exact OpenAPI evidence status required for a match.
`llms_txt`	No	Exact llms.txt evidence status required for a match.
`categories`	No	Exact category names. Supplying multiple category values allows a record to match any listed category; this category condition still combines with every other supplied filter group using AND logic.
`capabilities`	No	Capability terms that must all be present in the record's verified capabilities. Matching is case-insensitive and allows a capability string to contain the supplied term.
`min_readiness`	No	Strict minimum agent-readiness score. Records below this score are excluded.
`agent_actionable`	No	When true, require agent_actionable = true. False does not exclude actionable records; omit this field unless you need the positive requirement.
`agent_capabilities`	No	Agent capability dimensions that must all be explicitly present on a record.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`query`	No
`method`	Yes
`filters`	Yes
`results`	Yes
`returned`	Yes
`total_matches`	Yes
`evidence_policy`	Yes
`capability_graph`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 30, 2026
- addedOutput schema / properties / capability_graph
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / results / items / properties / capability_profile
```
Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / results / items / properties / capability_profile_url
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / results / items / properties / capability_summary
```
Added value: +{
+  "additionalProperties": true,
+  "type": [
+    "object",
+    "null"
+  ]
+}
```

Changed13 schema fields changedSep 27, 2026

addedInput schema / properties / a2a / description

Added value: +"Exact A2A evidence status required for a match."

addedInput schema / properties / agent_actionable / description

Added value: +"When true, require agent_actionable = true. False does not exclude actionable records; omit this field unless you need the positive requirement."

addedInput schema / properties / agent_capabilities / description

Added value: +"Agent capability dimensions that must all be explicitly present on a record."

addedInput schema / properties / capabilities / description

Added value: +"Capability terms that must all be present in the record's verified capabilities. Matching is case-insensitive and allows a capability string to contain the supplied term."

addedInput schema / properties / categories / description

Added value: +"Exact category names. Supplying multiple category values allows a record to match any listed category; this category condition still combines with every other supplied filter group using AND logic."

addedInput schema / properties / limit / description

Added value: +"Maximum number of matching records returned. Results are sorted by readiness descending then API name. total_matches still reports the full count. No pagination is currently exposed."

addedInput schema / properties / llms_txt / description

Added value: +"Exact llms.txt evidence status required for a match."

addedInput schema / properties / mcp / description

Added value: +"Exact MCP evidence status required for a match."

addedInput schema / properties / min_readiness / description

Added value: +"Strict minimum agent-readiness score. Records below this score are excluded."

addedInput schema / properties / openapi / description

Added value: +"Exact OpenAPI evidence status required for a match."

changedInput schema / properties / query / description

Previous value: -"Optional text search across name, provider, category, description, capabilities and auth."New value: +"Optional case-insensitive text search across API name, provider, category, description, capabilities, agent capabilities and authentication fields."

addedInput schema / properties / x402 / description

Added value: +"Exact x402 evidence status required for a match."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "evidence_policy": {
+      "type": "string"
+    },
+    "filters": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "method": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "a2a": {
+            "enum": [
+              "Yes",
+              "No",
+              "Unknown"
+            ],
+            "type": "string"
+          },
+          "agent_actionable": {
+            "type": "boolean"
+          },
+          "agent_capabilities": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "agent_readiness_score": {
+            "maximum": 100,
+            "minimum": 0,
+            "type": "number"
+          },
+          "auth_methods": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "authentication_verified": {
+            "type": "boolean"
+          },
+          "capabilities": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "category": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "docs_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "llms_txt": {
+            "enum": [
+              "Yes",
+              "No",
+              "Unknown"
+            ],
+            "type": "string"
+          },
+          "mcp": {
+            "enum": [
+              "Yes",
+              "No",
+              "Unknown"
+            ],
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "openapi": {
+            "enum": [
+              "Yes",
+              "No",
+              "Unknown"
+            ],
+            "type": "string"
+          },
+          "provider": {
+            "type": "string"
+          },
+          "public_documentation": {
+            "type": "boolean"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "website": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "x402": {
+            "enum": [
+              "Yes",
+              "No",
+              "Unknown"
+            ],
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "total_matches": {
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "name",
+    "method",
+    "filters",
+    "total_matches",
+    "returned",
+    "results",
+    "evidence_policy"
+  ],
+  "type": "object"
+}

AddedSep 26, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description goes further by disclosing cross-filter AND logic, the rule that Unknown never satisfies Yes, result sorting (readiness desc, then name), the 1-20 bound with default 10, and the absence of pagination. It stops short of describing the actual result payload shape, but the output schema covers that.

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?

Dense but front-loaded: purpose, then matching semantics, then result behavior, then the alternative. Every sentence carries information, though the sorting/limit detail is stated twice (once in prose, once in the limit schema description).

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?

For a 12-parameter filtered-search tool with an output schema and full annotation coverage, the description supplies everything needed to call it correctly, including match semantics and result sizing. Return values are correctly left to the output schema.

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 the baseline is 3, but the description adds cross-cutting semantics the per-parameter schema text does not: filter groups combine with AND, array capability filters require every supplied value, and exact protocol status means Unknown never matches Yes. That is meaningful behavior layered on top of already-documented parameters.

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?

States a specific verb (search) and resource (the canonical registry) and immediately scopes it to the case where the caller knows keywords or exact requirements. It also names the sibling it is not (search_capabilities), so an agent can distinguish it without opening either schema.

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?

Explicitly says when to use this tool ('already know keywords or exact requirements') and routes the capability-filter case to search_capabilities. The condition that selects the alternative is spelled out, not left to inference.

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

All RealWorldAPIs 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.