Skip to main content
Glama

Revoke an invitation

revoke_invite
Destructive

Revoke an invitation so it can no longer be accepted. Workspace owners only.

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": {
      "workspace_id": "<workspace_id>",
      "invite_id": "<invite_id>"
    },
    "name": "revoke_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
invite_idYes
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the bar is lower. The description adds two pieces of value beyond them: the post-condition (the invitation can no longer be accepted) and the authorization requirement (workspace owners only). It still omits whether revocation is reversible or what happens on a repeat call given idempotentHint=false.

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?

Two short sentences with no waste, and the purpose is stated before the access constraint. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter destructive tool with annotations covering the safety profile and no output schema, the description is roughly adequate. It is missing the source/format of invite_id and the behavior on repeat or already-accepted invites, which matters given idempotentHint=false.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: workspace_id is documented as coming from whoami, but invite_id has no description in either the schema or the tool description. The description does not say where an invite_id comes from or its format, so it fails to compensate for the coverage gap.

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 uses a specific verb and resource ("Revoke an invitation") and adds the effect ("so it can no longer be accepted"), which makes the outcome unambiguous. It does not explicitly contrast with siblings such as resend_invite or invite_member, so it falls 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?

The prerequisite "Workspace owners only" is a real usage constraint that tells the agent who can call it. However, there is no guidance on when to revoke versus resend or remove a member, and no mention of what to do if the invite was already accepted.

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