cozyvtt-mcp

Creature Search

creature_search

Read-onlyIdempotent

Search library templates for creatures to place as tokens later. Filter by name, challenge rating, or source; returns read-only results without creating characters or tokens.

Instructions

Search library templates for later placement with token_place_creature. Use character_list for campaign character sheets; this does not create either a character or a token. Read-only for campaign members. Explicit srd requires DND_5E; custom works across systems. Empty source searches both in DND_5E and custom otherwise. Search, challenge rating and offset are forwarded; limit is capped at 100 without local lower-bound validation. Repeating a search leaves the library unchanged. 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
`cr`	No	Challenge-rating filter passed as text, for example 1/2 or 3; empty omits it. Applicability is upstream-defined.
`limit`	No	Requested page size, normally 1..100; defaults to 20. Values above 100 are capped; other validation is upstream.
`offset`	No	Number of search results to skip, normally >=0; defaults to 0. Forwarded without local range validation.
`search`	No	Name/search filter passed upstream; empty string omits the filter.
`source`	No	srd or custom (case-insensitive); empty chooses both for DND_5E and custom for other or flexible campaigns.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.3.0Sep 20, 2026

addedInput schema / properties / cr / description

Added value: +"Challenge-rating filter passed as text, for example 1/2 or 3; empty omits it. Applicability is upstream-defined."

addedInput schema / properties / limit / description

Added value: +"Requested page size, normally 1..100; defaults to 20. Values above 100 are capped; other validation is upstream."

addedInput schema / properties / offset / description

Added value: +"Number of search results to skip, normally >=0; defaults to 0. Forwarded without local range validation."

addedInput schema / properties / search / description

Added value: +"Name/search filter passed upstream; empty string omits the filter."

addedInput schema / properties / source / description

Added value: +"srd or custom (case-insensitive); empty chooses both for DND_5E and custom for other or flexible campaigns."

First observedv0.1.0Sep 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark readOnly, openWorld, idempotent, and non-destructive, and the description reinforces and expands on this by stating no character/token is created and repeating a search leaves the library unchanged. It also discloses result and error shapes, which is valuable beyond 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 dense but each sentence adds necessary information about scope, alternatives, behavior, or return format. It is longer than minimal, but the complexity of the tool justifies the detail; the first sentence front-loads the core purpose.

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?

Given the annotations, full schema coverage, and output schema, the description is complete for an agent to call this tool correctly. It covers usage boundaries, source behavior, parameter forwarding semantics, idempotence, and success/error response shapes.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds meaningful behavioral context: search/cr/offset are forwarded, limit is capped at 100 with no local lower-bound validation, and empty source triggers different behavior across systems. This goes beyond the schema's field-level descriptions.

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 names a specific verb and resource: searching library templates for later placement with token_place_creature. It also distinguishes from character_list, explicitly stating this tool does not create a character or token, which prevents confusion with sibling 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?

It explicitly directs agents to use character_list for campaign character sheets, and clarifies when creature_search is appropriate. It also provides source-system selection guidance and states the read-only nature, giving clear context for when to invoke this tool over alternatives.

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