Skip to main content
Glama
flukeatzerocool

holonovel

by flukeatzerocool
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Faction

faction

Create, revise, remove, or list factions and their progress clocks in your novel. Use for faction management, not territory rooms.

Instructions

Manage organizations in the active Novel. Use when: creating, revising, removing, or listing factions and their progress clocks. Do NOT use when: tracking a faction's territory rooms — use world (action: create_room).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFaction name (create).
goalsNoOptional goals.
actionYescreate, update, remove, or list.
resourcesNoOptional resources.
territoryNoOptional territory names.
faction_idNoFaction identifier (update/remove).
descriptionNoOptional description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=false, so modification is expected. The description adds context about managing factions and progress clocks but does not detail side effects like deletion or state changes beyond that. It does not contradict annotations.

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?

Concise and well-structured, using 'Use when' and 'Do NOT use when' for clarity. No unnecessary words or redundant information.

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?

No output schema so return values are not needed. The description covers core actions and exclusions. Slight ambiguity remains about 'progress clocks' not being in the schema, but overall it is sufficient for an agent to decide when and how to use the tool.

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 descriptions cover all parameters with high coverage (100%), so the tool description adds no additional parameter semantics. 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?

Clearly states the tool manages factions (create, update, remove, list) and explicitly distinguishes it from the world tool for territory rooms. Specific verbs and scope leave no ambiguity.

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?

Provides explicit 'Use when' and 'Do NOT use when' conditions, referencing a sibling tool (world) and giving clear guidance on when to choose this tool.

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