Skip to main content
Glama
Sign In
Agent-Comm-Hub

Agent-Comm-Hub

by liuboacean
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

revoke_token

Invalidate an API token immediately to revoke access. Requires admin privileges.

Instructions

吊销 API Token，使其立即失效。仅 admin 可调用。

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": {
      "token_id": "<token_id>"
    },
    "name": "revoke_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_idYes要吊销的 Token ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.6

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description fully discloses the tool's behavior: it revokes a token immediately and requires admin privileges. This is straightforward for a mutation operation, though it does not detail consequences like non-admin attempts or idempotency.

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 extremely concise with two short sentences, no redundant words, and essential information front-loaded. Every sentence adds value.

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?

Given the tool's simplicity (one parameter, no output schema), the description provides adequate context: the action, effect, and access control. It could mention error handling for non-admin calls, but overall it is mostly complete.

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?

The input schema has 100% coverage for the single parameter 'token_id' with a clear description. The description adds no further meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 clearly states the action ('revoke'), the resource ('API Token'), and the immediate effect ('使其立即失效'), which translates to 'making it invalid immediately'. This distinguishes it from sibling tools, none of which handle token revocation.

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?

The description specifies a precondition ('仅 admin 可调用', 'Only admin can call'), providing clear context on who can use the tool. It does not explicitly state when not to use or mention alternatives, but the sibling list offers no similar tool, making the guidance sufficient.

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