apis-io

find_scopes

Read-only

OAuth scope catalogs across the catalog. The OAuth scopes an API defines. Understanding plan. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search. Priced B1 (single-entity synthesis) — $0.01 per call under pay-as-you-go; included in Understanding and Influence. See apis://prices.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No	Free text over name + description.
`page`	No
`sort`	No	Order: relevance / provider / name, or scope_count (largest first).
`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."

Changed2 schema fields changedSep 4, 2026

changedInput schema / properties / sort / description

Previous value: -"Order: name, or scope_count (largest first)."New value: +"Order: relevance / provider / name, or scope_count (largest first)."

changedInput schema / properties / sort / enum

Previous value: -[
-  "name",
-  "scope_count"
-]New value: +[
+  "relevance",
+  "provider",
+  "name",
+  "scope_count"
+]

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

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description correctly doesn't repeat safety. It adds value beyond annotations by disclosing pricing (B1, $0.01/call) and plan inclusion, plus the behavior of include=['content'] for inlining bodies. This is useful operational context not present in annotations.

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?

The description is three dense sentences: purpose, filtering guidance, alternative, and pricing. It is front-loaded with the core purpose and avoids fluff. The pricing info is relevant for cost-aware agents, so it earns its place.

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, the description covers the core purpose, key filters, a sibling alternative, and pricing, but it omits explanations for several parameters (page, limit, match) and doesn't describe the return format. It's adequate but not complete for a tool this complex.

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 44%, so the description must compensate. It explains q, tags, providers, and include in prose, but leaves page, limit, match, and context without additional meaning (context has a schema description, sort has one). It adds some value but doesn't fully cover the undocumented 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?

The description states the tool finds OAuth scopes across the catalog, a specific resource, and distinguishes it from find_artifacts by naming that sibling for cross-type search. The title 'Find OAuth scopes' reinforces the verb-resource pairing, so an agent can clearly tell this from the many sibling find_* tools.

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 'Use find_artifacts for cross-type search,' providing a clear alternative and condition. It also lists filterable fields (q/tags/providers) and the include parameter, giving direct usage guidance. It doesn't mention other siblings, but the main alternative is covered.

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?