Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

update-note

Update a map-note pin by moving, relabeling, resizing, toggling fog, or re-pointing to another journal page. Requires scene and note ID. GM only.

Instructions

Nudge ONE existing map-note pin by id (the legend→pins review loop): move it (x/y), relabel it, resize/restyle its icon, toggle fog global, or re-point it to a different journal/page. Patches only the fields you pass; at least one is required. Strict scene + note-id resolution. GM-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoNew pin X in absolute canvas pixels.
yNoNew pin Y in absolute canvas pixels.
iconNoNew Data-relative icon image src.
pageNoPage id or exact name within the (re-pointed) journal; only used with `journal`.
labelNoNew text shown on the pin.
globalNoRender the pin through fog/vision occlusion (NOT a permission control).
noteIdYesThe Note id to update (from create-scene-notes).
journalNoRe-point the pin to a different JournalEntry (id or exact name, strict resolve).
iconSizeNoNew icon size in px (min 32).
sceneIdentifierYesScene id or exact name holding the pin.
Behavior4/5

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

No annotations, so description covers behavior well: patches only passed fields, requires at least one field, strict resolution, GM-only. Does not detail error handling or return behavior.

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?

Two concise sentences front-load the purpose and provide necessary details without waste. Every word earns its place.

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 10 parameters, full schema coverage, no output schema, and no annotations, the description adequately covers patch behavior, restrictions, and usage. Could mention expected return or failure modes but not critical.

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 covers all parameters (100%), and description adds semantics like 'patches only fields you pass' and clarifies 'global' is not permission control, adding value beyond 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?

The description clearly identifies the tool as updating a single map-note pin by ID, with specific actions (move, relabel, resize, restyle, toggle fog, re-point). It distinguishes from sibling tools like 'create-scene-notes' and 'delete-note'.

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

Usage Guidelines4/5

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

Provides context ('legend→pins review loop') and requirements (strict resolution, GM-only), but does not explicitly state when to avoid using this tool or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Txpple/fvtt-mcp-molten5e'

If you have feedback or need assistance with the MCP directory API, please join our Discord server