MCP Platform Service

delete_entity

Delete a specified entity (user, project, task, or document) from the external platform by providing its unique identifier and type.

Instructions

Delete an entity from the external platform

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": {
      "entityId": "<entityId>",
      "entityType": "<entityType>"
    },
    "name": "delete_entity"
  }
}

Input Schema

Name	Required	Description	Default
`entityId`	Yes	The unique identifier of the entity to delete
`entityType`	Yes	The type of entity

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 6, 2026

TDQS

C2.9/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 disclose behavioral traits. It only states 'delete' without clarifying if the deletion is permanent, if it cascades to related data, or if any confirmation or permissions are needed. This is a significant omission for a destructive operation.

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?

Single sentence, very concise. No fluff. However, being too brief may omit necessary details for a destructive operation. For a simple delete, it is appropriately sized but could benefit from a brief behavior note.

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?

With no output schema, no annotations, and multiple sibling tools, the description is incomplete. It fails to explain return values (e.g., success/failure), error states, or prerequisites like authentication. Given the tool's destructive nature, more context is needed for safe usage.

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?

Input schema covers 100% of parameters with descriptions. The description does not add any additional meaning beyond what the schema provides (e.g., no clarification on what 'entityId' represents or how to obtain it). Baseline is 3 due to high schema coverage, and no extra value is added.

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?

Description states 'Delete an entity from the external platform', which clearly identifies the action (delete) and resource (entity). The input schema further specifies entity types, making purpose clear. However, it does not emphasize that deletion is permanent or irreversible, which could be implied. Sibling tools like create_entity and update_entity provide contrast, but the description does not explicitly differentiate 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 on when to use this tool vs. alternatives (e.g., update_entity for soft deletion or get_reference for verification). No prerequisites like authentication or validation steps mentioned. The description offers no context for appropriate usage scenarios.

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

Deploy Server