Skip to main content
Glama
Sign In
wuapi MCP server

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Cancel an invitation

cancel_invitation
DestructiveIdempotent

Cancel an invitation to disable its link instantly. Stops pending invitations from being used; completed invitations cannot be cancelled.

Instructions

Cancel an invitation: its link stops working. Completed invitations cannot be cancelled.

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": {
      "invitationId": "<invitationId>",
      "confirm": "<confirm>"
    },
    "name": "cancel_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. The invitation link stops working. Only set it after the user asked for this or agreed to it.
invitationIdYesThe invitation id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds useful behavioral context by stating that cancellation makes the link stop working and that completed invitations are exempt. This goes beyond what the annotations alone convey, though it does not discuss error behavior or reversibility explicitly.

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?

The description is two short sentences with no filler. The primary definition is front-loaded, and the completion constraint is stated in one additional sentence that earns its place.

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?

Together with the schema and annotations, the description covers purpose, effect, an important constraint, destructiveness, and the required confirmation flag. No output schema exists, but for a simple cancel operation the provided details are sufficient for an agent to invoke it correctly.

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%, so the parameter semantics are fully documented in the schema itself, including the confirm requirement. The description adds no additional parameter-level detail, so the baseline score of 3 is appropriate.

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 states a clear action and resource: "Cancel an invitation", plus the concrete effect "its link stops working". It also distinguishes the tool's scope by noting "Completed invitations cannot be cancelled", which is a meaningful boundary not present in sibling tool names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly gives a when-to-use rule: cancel an invitation by disabling its link, and an explicit when-not-to-use rule: completed invitations cannot be cancelled. It does not name alternatives like reset_group_invite_link, but the object-specific wording makes the intended use reasonably clear.

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

Deploy Server

Other Tools