kanka-mcp

Delete entity

kanka_delete_entity

Permanently delete a specified entity from a Kanka campaign. Requires confirmation to prevent accidental removal.

Instructions

Permanently delete an entity. Requires confirm: true to execute. Note: kanka_get_entity by entity_id may continue to succeed briefly via cache; pass an unknown entity_id to bust the resolver if needed.

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": {
      "campaign_id": "<campaign_id>",
      "entity_type": "<entity_type>",
      "id": "<id>",
      "confirm": "<confirm>"
    },
    "name": "kanka_delete_entity"
  }
}

Input Schema

Name	Required	Description	Default
`campaign_id`	Yes
`entity_type`	Yes
`id`	Yes
`confirm`	Yes
`entity_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 8, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It indicates the operation is permanent and requires confirmation, and it warns about caching effects. This is clear behavioral information, though it does not discuss reversibility or side effects on related data.

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?

The description is extremely concise: two sentences that front-load the purpose and key requirement. Every sentence adds value, with no wasted words. It is perfectly sized for a straightforward tool.

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?

The description covers the primary behavior and a caching caveat, but given the lack of output schema and annotations, it does not explain the return value or error scenarios. For a delete tool, knowing what to expect in response would enhance completeness. Without that, it is adequate but not complete.

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 coverage is 0%, so the description must compensate. It only explains the `confirm` parameter (must be true) and hints at `entity_id` for cache busting. The other parameters (`campaign_id`, `entity_type`, `id`) are not described, leaving significant gaps for a tool with 5 parameters.

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?

The description clearly states the tool deletes an entity permanently. It uses the specific verb 'delete' and resource 'entity', and the title 'Delete entity' reinforces this. It is distinct from siblings like kanka_create_entity, kanka_update_entity, and kanka_get_entity.

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 description explicitly requires `confirm: true` to execute, providing a key usage condition. It also gives a note about cache behavior for `entity_id`. However, it does not explicitly state when to use this tool versus alternatives, though the purpose implies its use for deletion.

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

Deploy Server