Off Shoring MCP

Export story

export_story

Export a story by ID as inline JSON or Markdown, including assignments, profiles, summaries, branches, turns, and statuses; treat exported dialogue as sensitive.

Instructions

Render a story as JSON or Markdown containing assignments, profiles, summaries, branches, turns and statuses. The document is returned inline in this result; it is not a downloadable file and no filesystem path is accepted or exposed. Exports can contain private dialogue, so treat the returned text as sensitive.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "story_id": "<story_id>"
    },
    "name": "export_story"
  }
}

Input Schema

Name	Required	Default
`format`	No	json
`story_id`	Yes
`max_chars`	No

Output Schema

Name	Required	Description
`ok`	No
`note`	Yes	Delivery note. The content is returned in this tool result; it is not a downloadable file and no server-local path is exposed.
`chars`	Yes
`format`	Yes
`content`	Yes
`story_id`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

B3.1/5.0

Behavior3/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 add real value: it states the document is returned inline, that no filesystem path is accepted or exposed, and that the payload may contain private dialogue requiring sensitive handling. It does not say whether the call is read-only, whether it has size or rate limits, or what happens when output is truncated — notable for a tool that renders an entire story.

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?

Three tight sentences, each doing distinct work: what is rendered, how it is delivered, and the sensitivity constraint. The delivery constraint is front-loaded where an agent will read it before forming assumptions about file output.

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?

An output schema exists, so return structure need not be explained, and the delivery/sensitivity notes cover the main non-obvious behavior. The definition is still incomplete for a three-parameter tool because max_chars, which governs output size and potential truncation, is left undefined.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 only covers one of three parameters: format, whose json/markdown enum values are at least echoed. story_id is unmentioned and max_chars is entirely unaddressed, leaving the truncation behavior of that parameter undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Render a story") plus the output formats and the exact content included (assignments, profiles, summaries, branches, turns, statuses). It is clearly distinguishable from list_stories or delete_story, though it never explicitly contrasts with the closer siblings get_story_context and read_turns, which an agent could reasonably confuse with a full export.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to choose export_story over get_story_context or read_turns, nor any prerequisite or exclusion guidance. The only guidance-like sentence addresses delivery mechanics (inline, no filesystem path), not tool selection.

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

Deploy Server