Skip to main content
Glama
Sign In

Caly

by com.trycaly
OverviewDiscussionsAdmin

Delete team

delete_team
Destructive

Delete a team with its event types and memberships. Owners only. A team with a running subscription must cancel it first (manage_subscription). Two steps: the first call returns CONFIRMATION_REQUIRED with a confirmToken; tell the user, then call again with the SAME arguments plus confirmToken.

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

Input Schema

NameRequiredDescriptionDefault
teamIdYesTeam ID from list_teams.
confirmTokenNoLeave empty on the first call. Then pass the token from the CONFIRMATION_REQUIRED answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint and non-idempotency, but the description adds what annotations cannot: the cascading deletion of event types and memberships, the owner authorization requirement, and the exact CONFIRMATION_REQUIRED/confirmToken round-trip on first call.

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?

Three compact sentences: effect, authorization, then the blocking precondition and confirmation protocol, all front-loaded with no filler or repetition.

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?

No output schema exists, yet the description compensates by describing the CONFIRMATION_REQUIRED return and confirmToken flow. Combined with the cascading-delete and permission facts, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are documented there, so the baseline is 3. The description still earns a lift by clarifying that the retry must repeat the SAME arguments alongside confirmToken, a nuance not present in the schema text.

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?

States a specific verb and resource ('Delete a team') plus its blast radius ('with its event types and memberships'), which distinguishes it from update_team, delete_organization, and leave_team in the sibling list.

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?

Gives explicit preconditions: owner-only access, and a running subscription must be cancelled first, naming manage_subscription as the alternative. The two-step confirmation protocol is spelled out rather than left to inference.

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

All Caly 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