Skip to main content
Glama
Sign In

Shager

by ai.shager
OverviewDiscussionsAdmin

Cancel a team invitation

cancel_invitation
DestructiveIdempotent

Cancels an invitation that is still waiting for an answer (list_members invitations): its link stops working at once. Needs the publish scope and a key whose human manages the team, like invite_member. Removing a member or changing someone's role isn't offered to agents (a misled agent could lock people out or hand out write access): the human does it on the Team page. (Not available in an unclaimed sandbox.)

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

Input Schema

NameRequiredDescriptionDefault
invitation_idYesid from list_members invitations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: it discloses the immediate invalidation effect, the required publish scope, the need for a key whose human manages the team, and the unclaimed-sandbox restriction. These are exactly the operational constraints an agent needs before calling a destructive mutation.

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 front-loaded with the action and effect, then adds permissions, alternatives, and sandbox restrictions in a tight sequence. Every sentence contributes useful information, and the parentheticals clarify rather than pad.

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?

For a one-parameter mutation with annotations and no output schema, the description covers the action, effect, required authorization, unavailable adjacent actions, and environment restriction. Nothing an agent needs to call it correctly is missing.

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 coverage is already 100%, and the schema description says the parameter is the 'id from list_members invitations.' The description repeats that same pointer without adding further syntax, format, or validation details, so the schema carries the parameter documentation.

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 specific verb and resource: it cancels an invitation that is still awaiting a response. It also specifies the exact effect ('its link stops working at once') and points to where valid invitation IDs come from (list_members). This clearly distinguishes it from invite_member, resend_invitation, and member-management tools.

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?

It explicitly says when to use the tool: only for pending invitations. It also states what is not available to agents (removing members or changing roles) and why those actions must be done by a human on the Team page. This gives clear boundaries against sibling tools.

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

All Shager toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources