Skip to main content
Glama

revoke_integration_grant

Destructive

Revoke an integration grant so it stops authorizing access on the next call. Revoked grants cannot be reactivated; create a new grant if access is needed again.

Instructions

Revoke a grant. Takes effect on the next call. A revoked grant cannot be reactivated — grant again instead. Repeating it returns the grant unchanged

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": {
      "grant_id": "<grant_id>"
    },
    "name": "revoke_integration_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
grant_idYesGrant to revoke

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.4

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds genuine context beyond them: timing ("takes effect on the next call") and irreversibility ("cannot be reactivated"). The note that repeating it "returns the grant unchanged" sits slightly in tension with idempotentHint=false, but reads more as clarifying the no-op response than as a true contradiction.

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?

Four short sentences, front-loaded with the action and followed by the behavior most likely to surprise an agent (delayed effect, irreversibility). Minor terseness ("next call" of what) keeps it below a 5.

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 one-parameter destructive tool with no output schema and rich annotations, the description covers the irreversibility, the effective timing, and repeat-call behavior — everything an agent needs before invoking it.

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 parameter whose schema description coverage is 100% ("Grant to revoke"), so the schema fully documents it. The description adds no format or semantics beyond that, making the baseline 3 appropriate.

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+resource ("Revoke a grant"), which is enough to distinguish it from siblings like ratify_integration_grant or list_integration_grants. It doesn't explicitly name the opposite operation (grant_integration) as a sibling, so it stops short of a 5.

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?

"A revoked grant cannot be reactivated — grant again instead" routes the agent toward the re-grant path, which is useful implied guidance, but it never names the alternative tool or states when revocation is the correct action versus ratifying or listing grants.

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