apis-io

find_json_schemas

Read-only

JSON Schemas across the catalog. Standalone data schemas. 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
`providers`	No

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

Changed1 schema field changedSep 2, 2026

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."

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.1/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, and the description adds that include=['content'] inlines bodies, which is a behavioral detail not in the schema. It doesn't contradict annotations and discloses the key filtering behavior.

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 with no fluff. The resource type is front-loaded, and the alternative is stated efficiently. Every clause adds value.

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?

For a 9-parameter tool with no output schema and low schema coverage, the description covers the essential filtering and the inline behavior but omits pagination, sorting, match semantics, and return format. These are left to the schema, which is incomplete for several params. It's adequate but not fully complete.

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 low (44%), and the description mentions only q, tags, providers, and include. It adds meaning for include (inlines bodies) but doesn't explain page, limit, match, or providers in detail. The schema descriptions for tags are oddly provider-focused, but that's not in the tool description. The description partially compensates for coverage gaps.

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 clearly states the tool finds JSON Schemas, specifying 'standalone data schemas' to distinguish from schemas embedded elsewhere. It names filtering options and explicitly differentiates from find_artifacts for cross-type search, so the purpose is unambiguous.

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 a clear alternative for cross-type search with find_artifacts, and implies this tool is for JSON schemas specifically. It doesn't explicitly mention when not to use it for other find_* variants, but the resource type makes the intended use clear.

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?