Skip to main content
Glama

面灵AI 面试助手

revoke_agent_grant

撤销一个 AI 助理的授权,该助理持有的令牌立即失效;撤销的若是当前这个助理自己的授权,之后的调用需用户重新授权。授权 ID 取自 list_agent_grants。(需要用户授权,范围 account:write)

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": {
      "grantId": "<grantId>"
    },
    "name": "revoke_agent_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
grantIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations it discloses the key behavioral facts: the assistant's token is invalidated immediately and self-revocation forces re-authorization on subsequent calls, plus the account:write scope requirement. It does not say whether the revocation is reversible or how to re-grant, and it does not address the mild tension with destructiveHint=false for an access-removing operation.

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?

Four short clauses, front-loaded with the action and its immediate consequence, then the edge case, then the parameter source and auth scope. Nothing is redundant.

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?

For a one-parameter mutation with no output schema, the description covers effect, self-revocation edge case, ID provenance, and required auth scope. Only reversibility and any error behavior for an invalid or already-revoked grant are left unstated.

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?

Schema coverage is 0%, so the description carries the burden; it supplies the practical meaning of grantId by naming list_agent_grants as its source, which is more than the bare string type in the schema. It does not describe the ID format, but the source pointer is sufficient to obtain a valid value.

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?

States a specific verb plus resource: revoking an AI assistant's grant, with the immediate effect that the assistant's token becomes invalid. It is cleanly distinguished from the sibling list_agent_grants, which is named as the ID source rather than a competing action.

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 tells the agent where the grantId comes from (list_agent_grants) and flags the special case of revoking the current assistant's own grant, which changes later behavior. It does not spell out an explicit when-to-use vs when-not-to-use rule, but the operation has no real sibling alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources