Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

oauth_revoke_client

Revoke an OAuth client to block new authentication. Deleting the client prevents further authorization while existing tokens remain valid until they expire.

Instructions

Revoke (delete) an OAuth client.

This will delete the client and prevent further authentication. Existing tokens will continue to work until they expire.

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_id": "<client_id>"
    },
    "name": "oauth_revoke_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYesClient ID to revoke

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

B3.4/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. It does usefully disclose that deletion blocks future authentication while existing tokens remain valid until expiry, but it omits permissions/authorization requirements, whether the operation is reversible, and what happens to existing tokens afterward (e.g., whether they can be force-revoked). For a destructive operation with zero annotation coverage, this is only partially adequate.

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?

Three short sentences, each earning its place: the action, the primary effect, and the important caveat about token lifetime. The destructive semantics are front-loaded.

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

Completeness4/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 documented, and the parameter is fully described in the schema. The remaining gap is authorization and reversibility context, which matters for a delete operation but is not covered.

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?

There is a single required parameter, and schema description coverage is 100% with the field already labeled "Client ID to revoke." The description adds no syntax, format, or source-of-value guidance beyond what the schema provides, so the baseline applies.

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 opens with a specific verb and resource ("Revoke (delete) an OAuth client") and immediately clarifies that revocation means deletion plus blocking future authentication. This distinguishes it from read-oriented siblings such as oauth_get_client_info and oauth_list_clients, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the destructive verb, but there is no explicit guidance on when to revoke versus when to use another path, no prerequisites or permission requirements, and no mention of alternatives such as oauth_register_client for re-creation.

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