Skip to main content
Glama

register_oauth_client

Register a new OAuth2 client to obtain Skilljar API credentials. Pick confidential to receive a secret or public for PKCE; save the secret now because it appears only once.

Instructions

Create a new OAuth2 client identity. THIS MINTS A CREDENTIAL.

    RFC 7591 Dynamic Client Registration. It is the only UNAUTHENTICATED call in
    this server: it does not use, and does not send, your Skilljar credentials.

    `client_name` is required, up to 255 characters. `redirect_uris`,
    `grant_types`, `scope` and `resource` are optional.

    `token_endpoint_auth_method` decides whether a secret is issued:
      `client_secret_post` (default) or `client_secret_basic` - a confidential
                           client, and a `client_secret` IS RETURNED
      `none`               a public/PKCE client, and NO secret is returned

    A RETURNED client_secret IS SHOWN ONCE AND CANNOT BE RETRIEVED AGAIN. There is
    no endpoint to read it back. If it is lost the client must be registered again.
    Hand it to a human to store; do not leave it sitting in a transcript.

    NO ORGANIZATION IS BOUND AT REGISTRATION. Skilljar does not associate a
    dynamically registered client with an organization or audit the registration, so
    a client made here is NOT a substitute for an organization-scoped credential
    issued through Skilljar. It will not read your courses.

    This tool is off unless the `admin` capability profile is enabled, even though
    Skilljar's own server ships it enabled.

    No OAuth scope is required, because no token is sent.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNo
resourceNo
client_nameYes
grant_typesNo
redirect_urisNo
token_endpoint_auth_methodNoclient_secret_post

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNo
warningYes
client_idYes
client_nameNo
grant_typesNo
client_secretNo
redirect_urisNo
token_endpoint_auth_methodNo
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

The description goes far beyond the annotations, disclosing critical behaviors: the client_secret is shown only once and can never be retrieved again, no organization is bound at registration, no audit is performed, and the tool is disabled without the admin capability profile. This is exactly the type of behavioral context an agent needs.

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 description is long but dense; every sentence contributes safety-critical or selection-critical information. It is front-loaded with the purpose and credential warning, and uses clear formatting with capitalized warnings and bullet-like examples for the token_endpoint_auth_method values.

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?

The description covers authentication behavior, availability, credential handling, organization scoping, parameter effects, and output expectations. With an output schema present, it does not need to document return structures, and it even explains the key return behavior (secret issued or not). Nothing essential is missing for an agent to decide and invoke this tool correctly.

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?

With 0% schema description coverage, the description carries the burden and largely succeeds. It explains that client_name is required and up to 255 characters, marks other parameters optional, and fully explains token_endpoint_auth_method including which values produce a secret. It adds more meaning than the bare schema, though it does not elaborate on scope, resource, or grant_types semantics.

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: 'Create a new OAuth2 client identity' and immediately clarifies that it mints a credential. It further distinguishes itself from organization-scoped credentials by stating it is not a substitute and will not read courses, which helps disambiguate from sibling create_oauth_client.

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?

The description explicitly states when to use it: it is the only unauthenticated call on the server and sends no Skilljar credentials. It also gives clear when-not guidance: it is not a substitute for an organization-scoped credential and requires the admin capability profile to be enabled.

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