Skip to main content
Glama
doitintl

DoiT MCP Server

Official
by doitintl

cancel_invite

Destructive

Cancel an outstanding user invite to the DoiT platform, invalidating the invite token while retaining the user record with a 'Cancelled' status.

Instructions

Manage users who have access to the DoiT platform. Marks the invite as Cancelled and invalidates the invite token so any outstanding email links stop working. The invite document is retained (soft cancel) — the user row remains visible in GET /iam/v1/users with inviteStatus: Cancelled. Use DELETE /iam/v1/users/{id} to fully remove the record.

Returns 404 if no invite exists for the given ID, and 409 if the invite is already cancelled.

Requires usersManager permission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
dryRunNo
Idempotency-KeyYes
customerContextNoScope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users.
Behavior5/5

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

Annotations already indicate destructive and non-read-only, but the description adds significant context: soft cancel behavior, retention of invite document, visible cancelled status, token invalidation, and error cases. No contradiction with annotations.

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?

The description is 6 sentences covering purpose, behavior, errors, and permissions. It is well-structured and front-loaded with key info, though the first sentence is somewhat generic ('Manage users...') and could be trimmed.

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?

No output schema exists, but the description explains the effect (soft cancel, token invalidation, status) and error codes. It mentions required permission. Lacks detail on dryRun and Idempotency-Key, but overall sufficient for a cancel operation.

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 25% (one parameter has description), and the tool description does not explain dryRun, Idempotency-Key, or the id format. The description only implies id is the invite ID. Given low schema coverage, the description should compensate but does not.

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?

The description clearly states the tool marks an invite as Cancelled and invalidates the token, distinguishing it from full deletion via DELETE. It specifies the verb and resource, and differentiates from sibling tools like delete_user and invite_user.

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?

Explicitly tells when to use this tool (soft cancel) versus DELETE for full removal. Also mentions error conditions (404, 409) and required permission (usersManager), providing clear context for when to invoke.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/doitintl/doit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server