Skip to main content
Glama

Delete Team Entry

team_delete_entry
Destructive

Soft-delete a team entry by marking it as deleted so it can be restored later; requires an expected version to prevent concurrency conflicts.

Instructions

Soft-delete a team entry (marks as deleted, preservable via team_restore_entry). Returns success: false for nonexistent entries. Requires TEAM_DB_PATH.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "team_delete_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idNo
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.
project_numberNo
expected_versionNoREQUIRED for safe deletion to prevent optimistic concurrency gaps. Get this from get_entry_by_id.

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
messageNo
successNo
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv9.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely new behavior: deletion is a soft mark that can be preserved/recovered, and the call returns success: false rather than erroring for missing entries. It also flags the TEAM_DB_PATH environment prerequisite, which is operational context no annotation carries. It does not mention that expected_version is required for safe deletion, which the schema alone conveys.

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, each front-loading the most decision-relevant fact (soft delete, recoverability, failure semantics). No filler and nothing that restates the title.

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?

For a destructive mutation, the description covers reversibility, error behavior, and an environment prerequisite, and an output schema means return shape need not be explained. The remaining gap is target identification across the four optional parameters, which is the main thing an agent could get wrong.

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

Parameters2/5

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

Schema description coverage is only 50%, and required parameters are zero, so the description carries real weight here — yet it says nothing about entry_id or project_number, or how they combine to identify the target. The only hint (nonexistent entries) touches entry_id obliquely; the concurrency/versioning requirement lives entirely in the schema.

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?

"Soft-delete a team entry (marks as deleted...)" gives a precise verb, resource, and the distinguishing semantic (soft vs hard delete) in one clause. It also names the paired recovery tool, team_restore_entry, so an agent can place it in the lifecycle without opening any schema.

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 recovery path (team_restore_entry) and the failure case for nonexistent entries give clear context for when this is the right call, plus a stated prerequisite (TEAM_DB_PATH). It stops short of explicitly contrasting with delete_entry, team_batch_delete_entries, or a hard-delete path, so the agent must infer single-vs-batch and team-vs-non-team selection.

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