apis-io

find_asyncapis

Read-only

AsyncAPI (event-driven) specifications across the catalog. Event/streaming APIs. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No	Free text over name + description.
`page`	No
`sort`	No	Order: relevance (catalog order), provider, or name.
`tags`	No	Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or find_providers?api_tags= to reach companies whose APIs merely touch it.
`limit`	No
`match`	No		any
`context`	No	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.
`include`	No
`version`	No	AsyncAPI spec version — the `asyncapi:` declaration, e.g. 2.6.0 or 3.0.0.
`providers`	No
`info_version`	No	The document's OWN version from info.version, set by whoever wrote the spec. Absent on 70% of them.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 17, 2026

changedInput schema / properties / tags / description

Previous value: -"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or api_tags below."New value: +"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or find_providers?api_tags= to reach companies whose APIs merely touch it."

Changed1 schema field changedSep 4, 2026

addedInput schema / properties / sort

Added value: +{
+  "description": "Order: relevance (catalog order), provider, or name.",
+  "enum": [
+    "relevance",
+    "provider",
+    "name"
+  ],
+  "type": "string"
+}

Changed3 schema fields changedSep 2, 2026

addedInput schema / properties / info_version

Added value: +{
+  "description": "The document's OWN version from info.version, set by whoever wrote the spec. Absent on 70% of them.",
+  "type": "string"
+}

changedInput schema / properties / tags / description

Previous value: -"Tag slugs."New value: +"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or api_tags below."

changedInput schema / properties / version / description

Previous value: -"AsyncAPI spec version, e.g. 2.6.0 or 3.0.0."New value: +"AsyncAPI spec version — the `asyncapi:` declaration, e.g. 2.6.0 or 3.0.0."

Changed1 schema field changedAug 27, 2026

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"
+}

AddedJul 16, 2026

TDQS

A4/5.0

Behavior3/5

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

readOnlyHint already covers safety; the description adds the include=content inlining behavior, which is useful. It does not mention pagination, response shape, or sorting defaults, but for a read-only search tool the annotations plus basic filter info are sufficient.

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 sentences, front-loaded with the tool's purpose and then the key usage guidance. No filler, no repeated schema content; every sentence earns its place.

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 read-only search tool with 11 parameters, the description covers the essential scope, filtering, and the sibling for broader search. No output schema exists, but the definition gives enough context to select and invoke the tool correctly in most cases.

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 55%, and the description clarifies the meaning of q, tags, providers, and especially include=content (inlines bodies). Other parameters like match, limit, and page are left to the schema or are self-evident, so the description adds marginal but useful value.

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?

Identifies a specific artifact type (AsyncAPI/event-driven specs) with catalog scope and explicitly distinguishes from find_artifacts. The phrasing 'Event/streaming APIs' reinforces the resource kind, leaving no ambiguity about what this tool searches.

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?

Provides concrete filtering options (q/tags/providers) and the include=content behavior, and names find_artifacts as the cross-type alternative. It doesn't contrast with every find_* sibling, but the one alternative given is the most relevant.

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

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

Resources

Need Help?