Skip to main content
Glama

AceRound AI Interview Copilot

revoke_agent_grant

Revoke an AI assistant's access; its tokens stop working immediately. Revoking the current assistant's own grant means the user must authorize it again. Grant ids come from list_agent_grants. (Requires the user's sign-in with scope 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.5/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing immediacy of effect, the self-revocation consequence, and the required user sign-in scope (account:write). Note the mild tension with destructiveHint=false: the description makes clear access is removed instantly, so an agent should treat the action as consequential even though the annotation does not mark it destructive. This is disclosed rather than contradicted.

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 compact sentences, front-loaded with the action and its effect, followed by the caveat, the id source, and the auth requirement. Nothing is redundant.

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?

For a single-parameter mutation with no output schema, the description covers everything an agent needs: what happens, how fast, the self-revocation hazard, where the identifier comes from, and the permission scope.

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 must carry the load; it does by explaining that grantId values originate from list_agent_grants, which the bare string parameter cannot convey. It does not explain format or the 64-character limit, but the provenance guidance is the substantive addition.

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 and resource ('Revoke an AI assistant's access') and immediately names the observable effect ('tokens stop working immediately'). The final sentence distinguishes it from the sibling list_agent_grants, which is the read-side counterpart.

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?

Tells the agent where grant ids come from (list_agent_grants) and flags the risky case of revoking the assistant's own grant, which forces re-authorization. It lacks an explicit 'do not use this when…' exclusion, but the context needed to choose correctly is present.

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