Skip to main content
Glama

item-create

Create a new item directly in an actor's inventory: custom items, loot, simple gear. SRD content: item-create-from-compendium; the world Items Directory instead of an actor: world-item-create.

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": {
      "actorId": "<actorId>",
      "name": "<name>",
      "type": "<type>"
    },
    "name": "item-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
imgNoItem icon path (optional)
nameYesItem name
typeYesItem type of the world's game system (dnd5e: weapon, equipment, consumable, tool, container, loot, spell, feat, class, …; "backpack" = legacy "container")
systemNoSystem data in the shape of the world's game system (dnd5e paths shown).
actorIdYesActor ID to add item to (from actor-list/actor-filter)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / system / description
      Previous value: -"D&D 5e system data."New value: +"System data in the shape of the world's game system (dnd5e paths shown)."
    • changedInput schema / properties / type / description
      Previous value: -"dnd5e item type (\"backpack\" is accepted as the legacy name of \"container\")"New value: +"Item type of the world's game system (dnd5e: weapon, equipment, consumable, tool, container, loot, spell, feat, class, …; \"backpack\" = legacy \"container\")"
    • removedInput schema / properties / type / enum
      Removed value: -[
      -  "weapon",
      -  "equipment",
      -  "consumable",
      -  "tool",
      -  "container",
      -  "loot",
      -  "spell",
      -  "feat",
      -  "background",
      -  "race",
      -  "class",
      -  "subclass",
      -  "feature",
      -  "facility",
      -  "backpack"
      -]
  2. Changed1 schema field changed
    • changedInput schema / properties / system / description
      Previous value: -"D&D 5e system data: quantity, weight, price, rarity, equipped, range, damage, uses, etc."New value: +"D&D 5e system data."
  3. Changed7 schema fields changed
    • removedInput schema / properties / system / properties / damage / description
      Removed value: -"Damage"
    • removedInput schema / properties / system / properties / damage / properties / base / properties / types / description
      Removed value: -"e.g. [\"slashing\"]"
    • removedInput schema / properties / system / properties / range / description
      Removed value: -"Weapon/spell range"
    • changedInput schema / properties / system / properties / range / properties / long / description
      Previous value: -"Long range (e.g. 600)"New value: +"e.g. 600"
    • changedInput schema / properties / system / properties / range / properties / reach / description
      Previous value: -"Melee reach in ft (default 5)"New value: +"reach ft"
    • removedInput schema / properties / system / properties / range / properties / units / description
      Removed value: -"ft or m"
    • changedInput schema / properties / system / properties / range / properties / value / description
      Previous value: -"Normal range (e.g. 150)"New value: +"e.g. 150"
  4. Changed7 schema fields changed
    • changedInput schema / properties / system / properties / uses / additionalProperties
      Previous value: -falseNew value: +true
    • addedInput schema / properties / system / properties / uses / properties / max / anyOf
      Added value: +[
      +  {
      +    "type": [
      +      "number",
      +      "string"
      +    ]
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / system / properties / uses / properties / max / type
      Removed value: -[
      -  "number",
      -  "null"
      -]
    • changedInput schema / properties / system / properties / uses / properties / per / description
      Previous value: -"Recovery: \"sr\", \"lr\", \"day\", \"charges\""New value: +"dnd5e 3.x"
    • addedInput schema / properties / system / properties / uses / properties / recovery
      Added value: +{
      +  "description": "[{ period: \"lr\" }]",
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "period": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "period"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / system / properties / uses / properties / spent
      Added value: +{
      +  "description": "dnd5e 4+: spent",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / system / properties / uses / properties / value / description
      Previous value: -"Remaining uses"New value: +"dnd5e 3.x"
  5. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the write/non-idempotent profile is covered by structured data. The description adds only that the item lands in the actor's inventory rather than the world, and says nothing about failure modes (unknown actorId, duplicate names, validation errors).

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?

Two compact sentences with the core action front-loaded and zero filler. The second sentence is telegraphic to the point of being slightly clipped ('the world Items Directory instead of an actor: world-item-create'), costing a little readability.

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

Completeness4/5

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

For a 5-parameter create tool with a nested free-form `system` object and no output schema, the description covers the what and the routing, and the schema fully documents the nested system shape. Only the return value and post-create behavior are left unspecified, which is acceptable given no output schema exists.

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 description coverage is 100%, including the actorId provenance hint ('from actor-list/actor-filter') and the dnd5e type enumeration, so the schema does the heavy lifting. The description's 'custom items, loot, simple gear' only loosely gestures at the type/system payload and adds no syntax beyond 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?

States a specific verb and resource ('Create a new item') and pins the destination ('directly in an actor's inventory'), then names the two sibling tools it is distinct from. An agent can separate it from item-create-from-compendium and world-item-create without opening any schema.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: SRD content goes to item-create-from-compendium, world-level items go to world-item-create, and this tool covers custom items, loot and simple gear. Both alternatives and the selecting condition are given.

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