Add a new race to a Kanka campaign by providing campaign ID and race details. Facilitates worldbuilding by creating the race entity through the API.
Create a new race
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| campaignId | Yes |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely states 'Create a new race' and says nothing about side effects, permissions, idempotency, required campaign context, or what happens on success or failure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short but it is under-specified rather than concise. The single phrase earns its place only by restating the function name, offering no substantive information to the agent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a required nested 'data' object, no output schema, no annotations, and zero schema descriptions, the description fails to provide basic invocation context. An agent cannot determine what data structure to send or what the response will be.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description adds no meaning to the parameters. The required 'data' object and 'campaignId' are completely undocumented, so an agent has no idea what to pass.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Create a new race' simply restates the tool name 'create_race' with no additional detail. It identifies the action and resource, but is purely tautological and does not differentiate this tool from the many other create_* siblings beyond the embedded resource name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. With a large sibling set including get_race, update_race, delete_race, and other create_* tools, the description offers no context or exclusionary conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.