Skip to main content
Glama

Use item

use-item

Use an actor's spell, ability, or consumable in Foundry VTT without waiting for GM confirmation. Targets active scene tokens and reports verified results.

Instructions

Start the use of an item of an actor (a spell, an ability, a consumable) in Foundry and return at once, without waiting for a dialog the Gamemaster may have to confirm. Targets are tokens of the active scene; if one cannot be found exactly, nothing is used. The adapter of the game system decides how the item is used and how consume and spellLevel apply; without one the usual item methods are tried, and failing those a plain chat message is posted. The answer says what was verified (targets, whether the use finished) and what was not (consumption).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
consumeNoLet the game system spend uses, resources or slots; true when left out
targetsNoTokens of the active scene to target, by token id, token name or actor name; "self" is the token of the actor. Leave out to keep the targets the Gamemaster has selected
spellLevelNoCast at this higher level, where the game system knows spell levels
itemIdentifierYesId or exact name of the item on that actor
actorIdentifierYesThe actor that uses the item. Id of the actor, its exact name (case does not matter) or the id of one of its tokens

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv14.2609.4

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the description doesn't need to restate those. It adds valuable behavioral context: the tool returns immediately without waiting for a GM dialog, targets must be found exactly or nothing is used, and the answer reports what was verified (targets, whether the use finished) and what was not (consumption). This goes beyond the annotations.

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?

The description is a single, dense paragraph that front-loads the core behavior and then explains fallback and return-value semantics. It is efficient and every sentence adds information. Slightly long, but justified given the complexity of the tool.

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?

Given the tool's complexity (5 params, no output schema, no enums), the description covers the key behavioral aspects: immediate return, target resolution, adapter behavior, fallback, and what the answer reports. It doesn't describe the exact return format, but the description explicitly says what the answer says, which is sufficient for an agent to know what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all five parameters. The description adds meaning by explaining the overall flow (how consume and spellLevel apply via the adapter, how targets are resolved, and what 'self' means). It doesn't repeat parameter details but provides context that helps an agent understand the semantics of the parameters in action.

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 description states a specific verb ('Start the use of an item'), the resource ('an item of an actor'), and the domain ('in Foundry'), and it distinguishes itself from sibling tools by clarifying it returns immediately without waiting for a GM dialog. It also names the game-system adapter behavior, which separates it from generic document/actor tools.

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?

The description explicitly explains when to use this tool: to start an item use and return immediately, without waiting for a GM confirmation dialog. It also gives fallback behavior when no adapter exists, and clarifies target resolution ('targets are tokens of the active scene; if one cannot be found exactly, nothing is used'). This is strong contextual guidance.

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