Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

oauth_register_client

Registers a new OAuth 2.1 client by providing a client name and redirect URIs, with optional grant types, scopes, and metadata for integration setup.

Instructions

Register a new OAuth 2.1 client.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "client_name": "<client_name>",
      "redirect_uris": "<redirect_uris>"
    },
    "name": "oauth_register_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
metadataNoOptional metadata dict
client_nameYesHuman-readable client name (e.g., "My OpenAI GPT")
grant_typesNoComma-separated grant types (default: "authorization_code,refresh_token")authorization_code,refresh_token
redirect_urisYesComma-separated redirect URIs
allowed_scopesNoComma-separated scopes (default: "read,write")read,write

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say whether registration is persistent or reversible, whether a client secret is generated and returned once, whether the call is idempotent, or what authorization is needed. For a security-sensitive mutation tool, this is a significant gap.

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?

A single front-loaded sentence with zero filler, which is structurally clean. Its brevity is not wasted wording, though it borders on under-specification for the operation it names.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but the tool has five parameters, a nested metadata object, and no annotations. Given that complexity and the sensitivity of issuing OAuth clients, the one-line description leaves the agent without enough context to call it confidently or know the consequences.

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 description coverage is 100%, including defaults for grant_types and allowed_scopes, so the baseline of 3 applies. The description adds no meaning beyond the schema — it never mentions comma-separated formatting, scope implications, or the metadata object.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Register a new OAuth 2.1 client'), which is unambiguous and distinguishable from the sibling names oauth_get_client_info, oauth_list_clients, and oauth_revoke_client. It stops short of explicitly naming or contrasting those alternatives, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, no prerequisites (e.g., whether an existing OAuth server/issuer must be configured first), and no exclusions. The agent must infer the trigger condition entirely from the tool name.

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

Deploy Server

Other Tools