Skip to main content
Glama
agentisend

agentisend

Revoke a connection

revoke_oauth_grant
DestructiveIdempotent

Disconnect one assistant by revoking its OAuth grant, immediately invalidating all its tokens and the key behind them. Provide the connection ID from list_oauth_grants; repeat calls return not_found.

Instructions

Purpose: disconnect one assistant. Every token it holds, and the key behind them, die immediately. NOT for: an assistant acting on its own. A key is refused with human_action_required. Do this in the console Connections page. Returns: the connection id and deleted: true. Repeating the call on an already-revoked id is not_found.

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_oauth_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
grant_idYesThe connection id from list_oauth_grants.
idempotency_keyNoYour own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect.

Output Schema

NameRequiredDescriptionDefault
idNoIdentifier.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
deletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description goes further by naming exactly what is destroyed (every token and the key behind them), the immediate effect, and the auth refusal mode (human_action_required). The note that repeating on an already-revoked id returns not_found usefully clarifies what 'idempotent' means in practice here rather than contradicting it.

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?

Labelled Purpose / NOT for / Returns sections keep it front-loaded and scannable, and every sentence carries distinct information (effect, exclusion, refusal mode, return, repeat behavior) with no padding.

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?

Given an output schema exists, the return summary is a bonus; the description still covers the destructive blast radius, the auth prerequisite, the alternative surface, and repeat-call semantics. Nothing an agent needs to call this safely is missing.

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?

Schema description coverage is 100% and both grant_id (with a pointer to list_oauth_grants) and idempotency_key are fully documented in the schema, so the description's references to 'the connection id' and repeat-call behavior add little beyond it. Baseline 3 for a high-coverage schema.

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 ('disconnect one assistant', every token and key it holds die immediately), which is unambiguous and distinct from the read-only sibling list_oauth_grants. An agent can tell exactly what this does without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit exclusion ('NOT for: an assistant acting on its own', refused with human_action_required) plus a concrete alternative path ('Do this in the console Connections page'). This is the full when/when-not/alternative triad.

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