Lunafic

Update world bible entry

update_entry

DestructiveIdempotent

Update an entry's metadata (name, tagline, description, tags, aliases, ...). Only provided fields change.

Input Schema

Name	Required	Description
`name`	No
`tags`	No
`type`	No	Change the entry type (e.g. character to lore). Refused for a character or role a story plays as.
`series`	No
`aliases`	No
`entryId`	Yes
`tagline`	No
`avatarUrl`	No
`inviteLine`	No	A character's Invite line: what they say in a push when a player has left a scene unfinished. One line, at most 160 characters; an empty string clears it.
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / inviteLine

Added value: +{
+  "description": "A character's Invite line: what they say in a push when a player has left a scene unfinished. One line, at most 160 characters; an empty string clears it.",
+  "type": "string"
+}

First observedOct 15, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false; the description adds the genuinely useful partial-update rule that only supplied fields are overwritten, which qualifies the destructive framing. It does not disclose that existing values are replaced, that missing assets/permissions can fail, or what happens to unset fields (clear vs no-op).

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 short sentences, zero filler, with the partial-update rule front-loaded right after the affected fields. Nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter mutation tool with 20% schema coverage and no output schema, the description leaves most parameters and the result (does it return the updated entry?) unexplained. An agent would still need to guess at semantics for entryId, series, avatarUrl, and how to clear a field.

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

Parameters2/5

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

Schema description coverage is only 20% (only 'type' and 'inviteLine' are documented). The description merely re-lists name, tagline, description, tags, aliases and trails off with '...', adding no meaning for entryId, series, avatarUrl, or clearing behavior on the remaining params. With such low coverage, the description should compensate and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb + resource ('Update an entry's metadata') with an enumerated field list, which clearly separates it from create_entry, delete_entry, and update_world. It does not name a sibling explicitly, but the update semantics are unambiguous.

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

Usage Guidelines3/5

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

'Only provided fields change' communicates partial-update semantics, which is real usage guidance. However, there is nothing on prerequisites (a valid entryId must already exist, likely obtained via search_entries/get_world_bible) and no when-not-to-use or pointer to alternatives.

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

All Lunafic tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?