cozyvtt-mcp

Token Place Creature

token_place_creature

Place a creature token on a map from a library template. Uses creature_search ID to copy name and image into a 1x1 token, without adding stats or character sheet.

Instructions

Create a visible 1x1 token from a library template's name and image (DM only). Use creature_search to obtain a template ID; use token_add for custom size, layer, controller, visibility, or a character link. This reads the template and copies only name/image into a token: it does not create a sheet or copy creature stats. Fails before creation if no usable image exists. Position must be within the map. Each accepted call creates another token. Returns upstream REST data without a broadcast receipt; use events_poll or the VTT to inspect subsequent visibility. Returns {ok:true,data} on success; tool-body failures return {ok:false,error} with optional diagnostic data. Argument-schema errors are MCP errors.

Input Schema

TableJSON Schema

Name	Required	Description
`x`	Yes	Horizontal position in map units; upstream requires 0 <= x < map width.
`y`	Yes	Vertical position in map units; upstream requires 0 <= y < map height.
`map_id`	Yes	Destination map ID in this campaign; discover dimensions through map_list.
`creature_id`	Yes	Library template ID from creature_search; the template must have a usable imageUrl, tokenImageUrl, or image.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.3.0Sep 20, 2026

addedInput schema / properties / creature_id / description

Added value: +"Library template ID from creature_search; the template must have a usable imageUrl, tokenImageUrl, or image."

addedInput schema / properties / map_id / description

Added value: +"Destination map ID in this campaign; discover dimensions through map_list."

addedInput schema / properties / x / description

Added value: +"Horizontal position in map units; upstream requires 0 <= x < map width."

addedInput schema / properties / y / description

Added value: +"Vertical position in map units; upstream requires 0 <= y < map height."

First observedv0.1.0Sep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The annotations already flag mutation and non-idempotency, but the description goes beyond them by disclosing that only name/image are copied, no sheet or creature stats are created, and each accepted call creates another token. It also reveals the response lacks a broadcast receipt and directs to events_poll or the VTT for visibility inspection, providing useful operational context.

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?

The description is dense and front-loaded with the primary purpose, then flows naturally into usage guidance, behavioral limitations, failure modes, and response format. Every sentence contributes a distinct piece of information, with no redundancy or filler, and the structure makes the tool's edge cases clear.

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?

The description covers the DM-only restriction, sibling tool routing, non-idempotent behavior, failure conditions, response format, and how to verify side effects via events_poll or the VTT. Combined with a complete input schema and an output schema, it leaves no critical gap for an agent to call and interpret the tool correctly.

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?

The input schema already describes all four parameters in full (100% coverage), so the description doesn't need to add much. It reinforces constraints like position within the map and usable image requirements, but offers no new parameter-level meaning beyond what the schema already states. The baseline of 3 applies because the schema carries the semantic load.

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 action and resource: 'Create a visible 1x1 token from a library template's name and image (DM only).' It also distinguishes itself from closely related siblings by explicitly routing creature_search for template lookup and token_add for custom size/layer/controller/visibility/character links, so an agent can clearly tell when this tool applies.

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?

It explicitly names the alternative tools and the conditions that select between them: creature_search for obtaining a template ID and token_add for custom token attributes. It also adds DM-only availability and defines failure conditions (no usable image, out-of-map position), giving agents a clear decision procedure.

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