Skip to main content
Glama

Revoke an invite link

appInvitesRevoke
DestructiveIdempotent

Turn ONE invite link off, named by the id appInvitesList returned (never the link or its token). Requires confirmed: true, representing the human’s agreement that THIS link should stop working; without the literal nothing is sent. Read outcome: revoked means it was active and no longer lets anyone in; redeemed means someone already opened it, so there was nothing to revoke — the person who opened it keeps their pass until it expires (up to 30 days), because a pass is a signed cookie the gateway set, not a session Tofu can end; not_found means nothing was there, so repeating a revocation is safe. Read appInvitesList afterwards to see what remains.

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": {
      "projectId": "<projectId>",
      "inviteId": "<inviteId>",
      "confirmed": "<confirmed>"
    },
    "name": "appInvitesRevoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteIdYes
confirmedYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
idYes
messageYes
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructive=true and idempotent=true, but the description goes far past them: it explains the consent gate, the three possible outcomes and their real-world consequences, and — critically — that a redeemed pass cannot be ended because it is a signed cookie, not a session. It even justifies why repeating a revocation is safe (not_found), which is the mechanism behind the idempotent hint rather than a restatement of it.

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?

Front-loaded with the action, then the precondition, then the outcome vocabulary in a single dense paragraph. Every clause earns its place, though the outcome enumeration is long enough that a bulleted or semicolon-separated layout would scan faster; a couple of phrases ('the person who opened it keeps their pass') could be tightened.

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?

Covers everything a destructive, human-consent-gated revocation needs: identifier provenance, the consent requirement, all outcome branches with their consequences, irreversibility limits, and the verification step. An output schema exists, so the description need not formalize return structure — and instead spends its words on meaning.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate — and it does: it tells the agent `id` must come from appInvitesList, not the link or token, and that `confirmed` must be literal true or nothing is sent. With a 64-char hex inviteId opaque in the schema, this is exactly the semantic guidance the schema lacks.

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 ('Turn ONE invite link off') plus the resource and its identifier source ('named by the `id` appInvitesList returned'), which distinguishes it from appInvitesCreate and appInvitesList. The 'never the link or its token' clause disambiguates the input shape an agent would otherwise get wrong from the schema alone.

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?

Explicit about when the call is legitimate ('Requires `confirmed: true`, representing the human's agreement') and names the follow-up action ('Read appInvitesList afterwards to see what remains'). It also flags the conditions under which the operation is a no-op, which is when-to-call guidance in reverse.

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