KSJ MCP Server

Overview Schema Source Related Servers Discussions Admin

set_volume

Configure which journal volume new captures go into and which volumes are visible to search and browsing. Call without arguments to view current settings.

Instructions

Configure journal volumes: which book new captures go into, and which
books are visible to search and browsing.

Volumes model multiple physical journals: volume 2 continues volume 1's
knowledge base (cross-volume connections are normal and expected). Set
current_volume once when starting a new book.

Args:
    current_volume: Volume for NEW captures (0 = leave unchanged).
    active_volumes: Read scope for search/list/connections tools:
                    "*" for all volumes, or a comma list like "2,3".
                    Empty = leave unchanged. journal_health and
                    knowledge_progress always see all volumes —
                    longitudinal KPIs over a truncated history would
                    mislead.

Call with no arguments to just see the current settings.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`active_volumes`	No
`current_volume`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.9.0Oct 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and largely meets it: it discloses sentinel semantics (0 / empty = leave unchanged, '*' = all), the read-only no-arg invocation, and the important scope exception that journal_health and knowledge_progress always see all volumes. It does not cover persistence, permissions, or reversibility, but the operational traits that matter for correct invocation are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose, then explains the volume concept, then documents each argument — a logical order with no wasted filler. The conceptual paragraph on multi-journal continuity is arguably longer than strictly necessary but it prevents an agent from mis-modeling volumes as independent.

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?

For a two-optional-parameter configuration tool with an output schema already supplied, everything an agent needs is present: purpose, invocation modes, sentinel values, and scope interactions with KPI tools. Nothing material is left for the agent to guess.

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?

Schema description coverage is 0%, so the description must compensate, and it does: current_volume is defined as the target for NEW captures with 0 meaning unchanged, and active_volumes is defined as the read scope with '*' and comma-list syntax plus empty meaning unchanged. Both parameters get meaning the schema alone cannot supply.

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?

Names a specific verb+resource (configure journal volumes) and states exactly what it governs: which book new captures land in and which books search/browsing can see. No sibling tool touches volume configuration, so it is trivially distinguishable.

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?

Gives concrete activation conditions: 'Set current_volume once when starting a new book' and 'Call with no arguments to just see the current settings.' It also scopes the effect of active_volumes against other tools. It stops short of explicitly naming an alternative tool, but none of the siblings performs this function.

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