Skip to main content
Glama
flukeatzerocool

holonovel

by flukeatzerocool
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Session

session

Manage session-level surfaces and diagnostics, including recapping activity, setting verbosity, ordering briefings, compressing logs, checking health, and subscribing to topics.

Instructions

Manage session-level surfaces and diagnostics. Use when: recapping recent activity (recap), setting output verbosity (verbosity), reordering briefing sections (briefing_order), compressing the audit log (compress), or reporting server health (health). Do NOT use when: recording story content — use story (action: record).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNonormal or terse (verbosity).
actionYesrecap, verbosity, briefing_order, compress, health, or subscribe.
topicsNoNotification topics to subscribe to (subscribe).
gm_notesNoGM-only free-text notes returned only to the Game Master badge (recap).
sectionsNoOrdered list of briefing sections (briefing_order).
max_entriesNoMaximum audit entries (compress).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.2
    • changedInput schema / properties / action / description
      Previous value: -"recap, verbosity, briefing_order, compress, or health."New value: +"recap, verbosity, briefing_order, compress, health, or subscribe."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "recap",
-  "verbosity",
-  "briefing_order",
-  "compress",
-  "health"
-]New value: +[
+  "recap",
+  "verbosity",
+  "briefing_order",
+  "compress",
+  "health",
+  "subscribe"
+]
    • addedInput schema / properties / gm_notes
      Added value: +{
+  "description": "GM-only free-text notes returned only to the Game Master badge (recap).",
+  "type": "string"
+}
    • addedInput schema / properties / topics
      Added value: +{
+  "description": "Notification topics to subscribe to (subscribe).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Added

TDQS

A4.1/5.0
Behavior3/5

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

The annotations indicate readOnlyHint: false, so the tool may modify state. The description mentions actions like 'compress' and 'reorder', implying state changes, but does not detail side effects or irreversibility. It adds some behavioral context beyond the annotation but lacks full transparency.

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 a single, focused paragraph with a clear structure: a summary, a list of use cases, and a negative instruction. It is concise and free of redundant information.

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

Completeness3/5

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

The description covers most actions but omits the 'subscribe' action present in the schema. It also does not explain the exact output or consequences of each action, leaving some gaps for a tool with multiple behaviors.

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?

The schema provides complete descriptions for all six parameters, and the tool description does not add significant clarification. Since schema coverage is 100%, the description's contribution is minimal, so a baseline score of 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?

The description clearly states the tool manages session-level surfaces and diagnostics, and enumerates specific actions (recap, verbosity, briefing_order, compress, health), plus a negative use case. This leaves no ambiguity about the tool's role.

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?

The description explicitly provides 'Use when:' and 'Do NOT use when:' conditions, giving the agent direct guidance on when to invoke this tool versus alternatives, such as the story 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