Skip to main content
Glama
Sign In
booking_chest

booking_chest

by dsddet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_team_membership

Remove a member from a team by providing the team ID and membership ID to cancel their association.

Instructions

Remove a member from a team.

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": {
      "team_id": "<team_id>",
      "membership_id": "<membership_id>"
    },
    "name": "delete_team_membership"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYesTeam ID
membership_idYesMembership ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. The description states 'Remove' implying a destructive action, but it does not mention side effects such as whether this affects future bookings, schedules, or other team data. It also does not specify the return value or error conditions. The tool is likely destructive, but no such hint is given.

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?

One sentence, no fluff. Every word is needed and clear. It is appropriately front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 params, no enums, output schema exists), the description is minimally adequate. The output schema is not shown, but context indicates it exists, so return values are not required in description. However, the lack of behavioral detail on side effects and usage context is a gap for a destructive operation.

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%, providing 'Team ID' and 'Membership ID' in the schema. The description adds no further meaning about these parameters, e.g., how to obtain the membership_id or whether membership_id is unique only within a team. Baseline 3 is appropriate given full schema coverage.

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?

The description is clear and direct: 'Remove a member from a team.' The verb 'Remove' combined with 'member' and 'team' leaves little doubt. It differentiates from siblings like 'create_team_membership', 'update_team_membership', and 'get_team_membership', though it does not explicitly contrast with them.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., 'delete_team' which removes the entire team, or 'update_team_membership' which might change role instead of removal). There are no prerequisites, no conditions on membership status, and no warning about consequences of removal.

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