Skip to main content
Glama
Sign In
MCP-Kanka

MCP-Kanka

by twistymaze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_posts

Update existing posts in Kanka campaigns by providing entity and post IDs. Optionally modify markdown content or hide from players.

Instructions

Update existing posts

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": {
      "updates": "<updates>"
    },
    "name": "update_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1.8/5.0
Behavior1/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 but fails to do so. It does not indicate whether this is a read-only or destructive operation, what permissions are required, potential side effects, or error handling, making it inadequate for a mutation tool.

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 only three words, front-loaded and free of unnecessary details. However, this conciseness comes at the cost of under-specification, but it earns full marks for brevity and structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the input schema (with nested objects and multiple required fields), lack of annotations, and no output schema, the description is severely incomplete. It fails to provide necessary context for a mutation tool, leaving critical gaps in understanding behavior and parameters.

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?

The schema description coverage is 0%, so the description must compensate but does not. It mentions no parameters, while the input schema includes a complex 'updates' array with nested objects and required fields like 'entity_id', 'post_id', and 'name'. The description adds no meaning beyond the schema.

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

Purpose2/5

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

The description 'Update existing posts' restates the tool name 'update_posts' with minimal elaboration, making it tautological. It specifies the verb ('update') and resource ('posts') but lacks detail about what aspects of posts are updated or how it differs from sibling tools like 'update_entities' or 'create_posts'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 does not mention prerequisites, context, or exclusions, such as when to choose 'update_posts' over 'update_entities' or 'create_posts', leaving the agent without 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

Other Tools