cozyvtt-mcp

Token Place Creature

token_place_creature

Place a visible 1x1 creature token on a map using a library template's name and image (DM-only). Supply a creature_search template ID and in-bounds x/y coordinates; fails if no usable image.

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; the template read is DM-only and upstream validates image access. 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

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

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.6/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), and the description goes well beyond them: DM-only read, failure before creation when no usable image exists, map-bound position constraint, per-call token creation, no broadcast receipt, upstream image-access validation, and a pointer to events_poll for visibility. It also discloses return shapes and the tool-body vs MCP error distinction.

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-loads the purpose and routing guidance before the behavioral detail, and most sentences carry distinct information (failure mode, DM-only, repeat-creation, error shapes). It is somewhat dense and there is minor redundancy re-stating the return shape despite an output schema, but nothing is wasted.

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 4-required-param mutation with full schema coverage, annotations, and an output schema, the description covers every decision-relevant gap: prerequisites, DM-only scope, failure conditions, non-idempotency, and how to observe results. Nothing an agent needs to invoke it correctly 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 description coverage is 100%, so the schema already documents all four parameters including the image-source requirement and the x/y bounds. The description's 'Position must be within the map' and image references restate rather than extend the schema, so the baseline 3 is appropriate.

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 visible 1x1 token from a library template') and immediately scopes it (DM only). It explicitly contrasts itself with the sibling token_add, so an agent can differentiate the two without reading either 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?

Explicitly routes the agent: 'use creature_search to obtain a template ID' for the prerequisite, and 'use token_add for custom size, layer, controller, visibility, or a character link' for the alternative. This is a textbook when/when-not/alternative breakdown.

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