Off Shoring MCP

Create story

create_story

Create a saved story with scene setup and editable character assignments to initialize fiction records without starting a conversation.

Instructions

Create a story with a scene setup and editable character assignments. Writes local fiction records: this creates saved state, it does not begin a conversation. If idempotency_key is supplied, a retry with the same key and arguments returns the original result instead of creating a second story.

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": {
      "title": "<title>"
    },
    "name": "create_story"
  }
}

Input Schema

Name	Required	Default
`setup`	No
`title`	Yes
`summary`	No
`profiles`	No
`user_role`	No	Rasp
`assistant_role`	No	Cantor
`idempotency_key`	No

Output Schema

Name	Required	Description
`ok`	No
`story`	Yes
`profiles`	Yes
`root_branch`	Yes
`idempotent_replay`	No	True when this result was replayed from an earlier identical call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

B3.4/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 does disclose the important traits: this is a write that creates saved local state, and idempotency_key makes retries safe by returning the original result. It leaves unstated what happens on title collisions and how profiles interact with the user_role/assistant_role defaults.

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?

Three sentences, front-loaded with the action, then the state-write caveat, then idempotency semantics; nothing is padding. The opening clause 'with a scene setup and editable character assignments' is slightly vague for the space it occupies.

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 values need not be explained, and the mutation/idempotency behavior is well covered. For a 7-parameter creation tool with zero schema descriptions, though, the definition leaves too much parameter meaning to inference.

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% at the top level, so the description must compensate and largely does not. It gestures at 'scene setup' and 'character assignments' and explains idempotency_key semantics, but says nothing about title, summary, user_role/assistant_role defaults ('Rasp'/'Cantor'), or the relationship between profiles and those role fields.

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?

States a specific verb and resource ('Create a story') and adds scope detail (scene setup plus editable character assignments). The clarification 'it does not begin a conversation' helps separate it from turn/append-oriented siblings, though it never names a sibling tool directly.

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

Usage Guidelines3/5

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

Usage is implied by the creation semantics and the explicit exclusion ('does not begin a conversation'), which rules out one wrong path. It gives no positive routing guidance, such as when to use create_story versus update_story or branch_story, and states no prerequisites.

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

Deploy Server