Skip to main content
Glama
Sign In
booking_chest

booking_chest

by dsddet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_team

Remove a team from your booking system by providing its team ID to permanently delete the team and all associated data.

Instructions

Delete 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>"
    },
    "name": "delete_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYesTeam ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist to describe behavior. The description only states 'Delete a team' but fails to disclose key behavioral traits like irreversibility, cascading deletion of associated resources (e.g., members, event types, webhooks), required permissions, or error conditions. For a destructive mutation operation, this lacks essential transparency.

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 a single, concise sentence of only 3 words. It is front-loaded and efficient, with no unnecessary text. However, it may be too terse given the need for behavioral transparency.

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

Completeness2/5

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

Given the complexity of a 'delete' operation with potential irreversibility and cascading effects, the description is incomplete. Although there is an output schema, the description should clarify what happens when a team is deleted (e.g., deleted team members, event types, webhooks). It lacks sufficient context for an agent to safely use this tool.

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%, with the single 'team_id' parameter described as 'Team ID' in the schema. The description adds no additional semantic context beyond that. Baseline score 3 is appropriate since the schema already provides adequate parameter documentation.

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 'Delete a team' clearly states the action (delete) and the resource (team). It is specific and distinct from sibling tools like 'create_team', 'update_team', 'get_team', and 'list_teams', making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., permissions needed, whether the team must be empty), potential side effects (e.g., what else gets deleted), or when to avoid using it.

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