Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Remove an extra skill from a World

imagine_remove_world_skill
DestructiveIdempotent

Remove one of a World's extra skills. Skill rows Characters already have stay on their sheets. Returns { success: true }; 404 for an unknown skill. Only the World's owner, a contributor, or an admin with Admin Mode on may do this. Destructive. Confirm with the user first.

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": {
      "id": "<id>",
      "skillId": "<skillId>"
    },
    "name": "imagine_remove_world_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMongo `_id` of the World.
skillIdYesThe extra skill's `_id`, from imagine_list_world_house_rules (`houseSkills[]._id`).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint and idempotent, yet the description adds genuinely new behavior: the exact success payload, the 404 on an unknown skill, the authorization roles required, and the fact that character sheets are untouched. That is exactly the extra context annotations cannot convey.

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?

Five short sentences, each carrying a distinct fact, with the core action and side-effect clarification front-loaded and warnings trailing. The brief return-value clause is redundant with the output schema but is paired with the 404 note, so it still earns its place.

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

Completeness5/5

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

For a two-parameter destructive mutation, the definition covers action, side effects, authorization, failure mode, and confirmation policy; the output schema handles return shape. Nothing an agent needs in order to call it safely is missing.

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?

Schema coverage is 100% and the schema itself documents both `id` (World Mongo `_id`) and `skillId` with a pointer to where to obtain it via imagine_list_world_house_rules. The description adds no further parameter meaning, so the baseline of 3 applies.

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?

States a specific verb and resource ("Remove one of a World's extra skills") and immediately scopes the blast radius with "Skill rows Characters already have stay on their sheets." An agent can distinguish this from add/update skill siblings purely from the verb and the scope note.

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?

Gives clear preconditions: only the World's owner, a contributor, or an admin in Admin Mode may call it, and it instructs confirming with the user first. It does not explicitly name an alternative tool (e.g. add/update skill), but the removal semantics make the alternative obvious.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources