Skip to main content
Glama
flukeatzerocool

holonovel

by flukeatzerocool
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Vow

vow

Track narrative oaths, quests, and obligations with milestones. Set, advance, resolve, forsake, or list them to keep story continuity.

Instructions

Track narrative vows, quests, and obligations with milestones. Use when: setting, advancing, resolving, forsaking, or listing vows. Do NOT use when: starting a clock timer — use countdown (action: set).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoVow name (set).
scopeNogm, shared, faction, or party (set).
actionYesset, milestone, resolve, forsake, or list.
reasonNoThe reason for abandoning (forsake).
outcomeNoThe resolution outcome (resolve).
partiesNoParties bound by the vow (set).
vow_nameNoVow name (milestone/resolve/forsake).
difficultyNotroublesome, dangerous, formidable, extreme, or epic (set).
descriptionNoVow description (set).
consequencesNoOptional consequences (resolve).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A5/5.0
Behavior5/5

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

The description names each action and its effect (e.g., resolving requires an outcome, forsaking requires a reason). Annotations indicate readOnlyHint is false, so the mutating nature is consistent. No contradictions or hidden side effects.

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 just two sentences, yet conveys purpose, use cases, and a critical exclusion. It is well-structured and free of unnecessary detail.

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 schema covers all parameters and the description explains the actions and their parameters, the tool is fully specified for an agent. No output schema is needed for a mutation tool, and the openWorldHint annotation aligns with the narrative context.

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?

All 10 parameters have descriptions, and the schema description coverage is 100%. Each parameter's description includes the action it applies to (e.g., 'Vow name (milestone/resolve/forsake)'), which clarifies conditional usage.

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 states the tool tracks narrative vows with milestones and lists the five actions (set, milestone, resolve, forsake, list). It also distinguishes itself from the countdown tool, making its purpose unambiguous.

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 states when to use (setting, advancing, resolving, forsaking, listing vows) and provides a negative instruction ('Do NOT use when: starting a clock timer — use countdown'), which is excellent guidance for an agent.

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

Deploy Server

Other Tools