Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Change a World's extra skill

imagine_update_world_skill
Idempotent

Change the name, ability, or description of one of a World's extra skills; only the fields you send change, and the skill keeps its ruleset. Skill rows already on Characters' sheets do not change. Takes no baseUpdatedAt: the app changes only the fields sent. Returns { houseSkill }; 409 when the new name is taken in the skill's ruleset, 404 for an unknown skill. Only the World's owner, a contributor, or an admin with Admin Mode on may do this.

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_update_world_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMongo `_id` of the World.
nameNoNew skill name. The app answers 409 for a name the World already has in the skill's ruleset.
skillIdYesThe extra skill's `_id`, from imagine_list_world_house_rules (`houseSkills[]._id`).
attributeNoThe ability the skill is rolled with, written the way a Character's skill rows of that ruleset write it in `skills[].attribute` (read one with vault_get_character).
descriptionNoNew description.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=true), it discloses that skill rows already on Character sheets are not cascaded, that the ruleset is preserved, that no baseUpdatedAt is required, the response shape, and the 409/404 failure modes. The permission model (owner, contributor, or admin with Admin Mode) is also stated, and nothing contradicts the idempotent/non-destructive hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then consequences, return value and errors — good ordering. It is slightly redundant, however: 'only the fields you send change' and 'Takes no baseUpdatedAt: the app changes only the fields sent' restate the same patch behavior in consecutive sentences.

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 5-param patch tool with full schema coverage, annotations, and an output schema, the description covers everything an agent needs: scope, non-cascading behavior, concurrency-token omission, error codes, and authorization. No gap remains that would cause a misinvocation.

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 already documents each field, so the baseline is 3. The description adds some meaning — patch semantics for optional fields and the rationale for the absent baseUpdatedAt — but does not explain the attribute format beyond noting it mirrors a Character's skills[].attribute, which is already covered in the schema.

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 first clause states a specific verb and resource ('Change the name, ability, or description of one of a World's extra skills'), and the sibling set (add/remove world skill) makes the mutation boundary unambiguous. An agent can tell this is a field-level patch of an existing skill rather than create or delete.

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?

Usage context is clear: it is the tool for modifying an existing extra skill, with patch semantics spelled out ('only the fields you send change'), and the permission precondition is given. It does not explicitly name add/remove siblings as alternatives, but the scoping language makes selection 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