KSJ MCP Server

Overview Schema Source Related Servers Discussions Admin

manual_capture

Stores journal captures from transcribed text, primarily for handwritten pages read via AI vision. Confirms transcription and saves with template and volume support.

Instructions

Store a journal capture from transcribed text. This is the PRIMARY path
for handwritten pages: the user shares a photo of the page, YOU (the
assistant) read it with vision, confirm the transcription with the user,
then call this tool with the text. Assistant vision is far more accurate
on handwriting than local OCR — prefer this over upload_capture whenever
the user can show you the page.

Transcribe faithfully: keep field labels (First Impressions, Key Points,
Tags, etc.) as written, include every schema tag (#topic @source !priority
?question $insight *sensory), and treat content inside tag bubbles as tags.

Accept-by-default: the capture is always stored. A template ID that
can't be parsed or found, or a page ID already taken in that volume,
files it as a Wild Art (WA) entry with the reason recorded — nothing is
rejected and nothing is overwritten.

3-D isometric grid pages have their own type: pass template_id="ISO-001"
(etc.) — transcribe the subject line, labels, and notes around the drawing.

Args:
    text:        The transcribed content of the journal page (all fields
                 you can read — First Impressions, Key Points, Tags, etc.).
    template_id: Template ID (e.g. "RC-001", "ISO-002"). If omitted, the
                 server will try to detect it from the text automatically.
                 Pass "WA" to file the capture as Wild Art by hand.
    force:       Set to True to REPLACE an existing capture with the same
                 template ID in the same volume (default False — the new
                 capture is filed as WA with reason id_conflict instead).
    volume:      Which journal/book this page belongs to. 0 = automatic:
                 a volume written on the page/text wins, otherwise the
                 stored current_volume setting (default 1).
    wa_reason:   File as Wild Art on purpose. Use "loose_capture" for
                 anything off-journal — a napkin sketch, sticky note,
                 whiteboard photo, back of a receipt (no volume or page ID
                 needed). Other values: manual, other.
    wa_detail:   Free-text note for a WA entry, e.g. "napkin", "sticky note".

Returns the same summary as upload_capture, including any connections
detected to existing captures.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes
`force`	No
`volume`	No
`wa_detail`	No
`wa_reason`	No
`template_id`	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.9/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: accept-by-default means nothing is rejected and nothing is overwritten, unparseable template/page collisions fall back to a Wild Art entry with a recorded reason, and force=True replaces rather than duplicates. These are non-obvious side effects an agent must know before calling.

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-loaded with purpose and the primary-path routing before the behavioral caveats and the Args block. It is long, but nearly every sentence carries distinct operational information (faithful transcription, tag handling, accept-by-default). Slightly dense rather than bloated.

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?

An output schema exists, so return values need not be detailed, and the description still notes the return mirrors upload_capture including detected connections. For a 6-param mutation tool with zero annotation coverage, all behavioral and parameter gaps are filled.

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 documents all six parameters with defaults and semantics: volume 0 = automatic with volume-wins-over-current_volume precedence, force replacement vs. WA-with-id_conflict default, wa_reason accepted values, and free-text wa_detail. This goes well beyond the bare schema.

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?

Opens with a specific verb+resource: 'Store a journal capture from transcribed text', and immediately positions itself against the sibling upload_capture as the PRIMARY path for handwritten pages. An agent can distinguish this from upload_capture, correct_ocr, and bulk_upload without opening any schema.

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?

Gives explicit routing: prefer this over upload_capture whenever the user can show you the page, because assistant vision beats local OCR. It also spells out when to pass template_id='ISO-001', when to pass 'WA', and when to hand-file with wa_reason='loose_capture'. When-to-use, when-not, and alternatives are all present.

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