Skip to main content
Glama

Revoke an invitation

company_invite_revoke
DestructiveIdempotent

Revokes a pending invitation so its link stops working immediately. Owners and admins (admins only for member or viewer invitations). Call without confirm first for a preview, then again with confirm and the preview_token.

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": {
      "company": "<company>",
      "invitation": "<invitation>"
    },
    "name": "company_invite_revoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany ref (CO-XXXXXXXX) from company_list_mine.
confirmNoSet true only on the second call, after the user approved the preview.
invitationYesInvitation ref (IV-XXXXXXXX) from company_invitations_list.
preview_tokenNoThe preview_token returned by the first call (same input).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description adds real context beyond them: the link dies immediately, there is an authorization tier that varies by invitation role type, and the mutation is gated behind a preview/confirm exchange. That is the permission and consequence information an agent needs before a destructive write.

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 short sentences, front-loaded with the action and effect, then authorization, then the call sequence. No redundant restatement of the title or schema fields.

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 destructive, no-output-schema mutation this covers effect, permissions, and the confirm-token workflow well. The only gap is what the preview call returns beyond the preview_token, which an agent may want before deciding whether to surface the preview to the user.

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 100% and each parameter is already documented in the schema, so the baseline is 3. The description goes one step further by explaining the relationship between the calls ('call without confirm first … then again with confirm and the preview_token'), which is the semantics a per-field schema cannot convey; it stops short of describing the preview payload itself.

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 ('Revokes') and resource ('a pending invitation') plus the concrete effect ('its link stops working immediately'), which is more precise than a bare 'revoke invitation'. It is unambiguous against siblings like company_invite_create and company_invite_resend without needing to name them.

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 explicit preconditions (owners and admins; admins only for member or viewer invitations) and a prescribed call sequence: call without confirm for a preview, then again with confirm and the preview_token. An agent knows both who may call it and how to invoke it in the intended two-step flow.

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