Skip to main content
Glama

Coline

Revoke an invite

revoke_invite
DestructiveIdempotent

Revokes a pending invite, so its link stops working.

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": "<workspace>",
      "inviteId": "<inviteId>"
    },
    "name": "revoke_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteIdYesinviteId from list_members.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
revokedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description's added value is the concrete effect (the link stops working), but it omits whether the invite record is deleted or just invalidated, what error an already-accepted invite produces, and what permissions are required.

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?

A single eighteen-word sentence with the action front-loaded and the effect trailing as a consequence. Nothing is padded or repeated from the title or annotations.

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?

This is a simple two-parameter mutation with full schema coverage, complete annotations, and a published output schema, so the description need not explain return values. What remains missing is the edge-case behavior for non-pending invites and the permission requirement, which keeps it from a 5.

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% — both inviteId ("from list_members") and workspace ("slug from workspaces.list") are fully documented in the schema. The description adds nothing about the parameters, so the baseline 3 applies.

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?

Names a specific verb and resource ("Revokes a pending invite") and adds the observable consequence ("its link stops working"), which is more than a restatement of the title. It stops short of naming the sibling it differs from (e.g. extend_invite), so an agent must infer that boundary.

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 adjective "pending" implies the tool applies only to invites that have not yet been accepted, which is useful scoping, but the description never states what happens for non-pending invites or points to extend_invite as the alternative when the goal is to keep the invite alive. Usage is implied rather than spelled out.

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