MCP-Kanka

create_entities

Create multiple entities like characters, locations, or quests in a Kanka campaign with a single request. Specify entity type, name, and optional details like description and tags.

Instructions

Create one or more entities

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": {
      "entities": "<entities>"
    },
    "name": "create_entities"
  }
}

Input Schema

Name	Required	Description	Default
`entities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Feb 22, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates entities but doesn't mention permissions required, whether creation is reversible, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency about its operational behavior.

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 with a single sentence 'Create one or more entities'. It's front-loaded and wastes no words, making it easy to parse quickly. Every word earns its place by conveying the core action and resource without unnecessary elaboration.

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 creating entities with multiple nested properties, no annotations, and no output schema, the description is incomplete. It doesn't explain the entity types, required fields, or what the tool returns, leaving significant gaps for the agent to infer from the schema alone. This is inadequate for a tool with such rich input structure.

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?

The description has 0% schema description coverage, but it compensates by implying the 'entities' parameter is an array of objects to create. However, it doesn't detail the structure or required fields beyond what the schema provides. Since there's only 1 parameter, the baseline is high, but the description adds minimal semantic value beyond the schema's explicit properties and enums.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create one or more entities' clearly states the action (create) and resource (entities), but it's vague about what 'entities' are in this context. It doesn't distinguish this tool from sibling tools like 'create_posts' or explain what types of entities can be created, leaving the purpose somewhat ambiguous despite having a basic verb+resource structure.

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 doesn't mention sibling tools like 'update_entities' or 'delete_entities', nor does it specify prerequisites, contexts, or exclusions for creation. This lack of comparative context leaves the agent without clear usage direction.

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

Deploy Server