Skip to main content
Glama

list_oauth_scopes

Read-onlyIdempotent

Lists all OAuth scopes and named preset bundles the API defines, with descriptions and categories. Check before creating or narrowing a client to identify valid scopes and enable least-privilege access.

Instructions

List every OAuth scope this API defines, and the named preset bundles.

    Read this BEFORE creating or narrowing a client — it is the authoritative list
    of what `scope_codenames` accepts, with a description and category for each, and
    it is what makes least-privilege possible rather than guesswork.

    `presets` are named bundles Skilljar maintains, usable as `scope_preset` instead
    of listing codenames one by one.

    The catalogue is served from in-memory constants upstream, so it reflects what
    the API defines, which is not necessarily what any given client was granted.

    Requires the `clients:read` OAuth scope, and the `admin` capability profile.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
scopesYes
presetsYes
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses that the catalogue is served from in-memory constants upstream, so it reflects API definitions rather than any given client's actual grants. It also states the required OAuth scope and capability profile, adding real behavioral context.

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 summary sentence is front-loaded, and each subsequent sentence adds a distinct piece of value: when to use it, what presets are, data-source caveat, and auth requirements. Nothing feels redundant or padded.

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 parameterless read-only listing tool with an output schema and strong annotations, the description covers purpose, usage timing, data semantics, and access requirements. An agent has everything it needs to decide when and how to invoke this tool.

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?

The tool has zero parameters, so the baseline is high and there is little to explain. The description adds relevant context about what the returned scope codes mean and how presets relate, even though no parameter documentation is needed.

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 opens with a specific verb and resource: lists every OAuth scope and preset bundles defined by the API. It clearly distinguishes itself from sibling client-management tools by positioning itself as the authoritative reference for accepted scope_codenames.

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?

It explicitly instructs the agent to read this tool before creating or narrowing a client, and explains that it makes least-privilege selection possible rather than guesswork. It also clarifies how presets fit in as an alternative to listing codenames individually.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CloudSecurityAlliance/csa-skilljar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server