Off Shoring MCP

List stories

list_stories

Return compact, read-only summaries of stored stories—title, IDs, revision, latest update, and turn/branch counts—ordered by newest update with limit and offset.

Instructions

Return compact summaries of stored stories (title, ids, revision, latest update, turn and branch counts), newest update first. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_stories"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Output Schema

Name	Required	Description
`ok`	No
`limit`	Yes
`total`	Yes
`offset`	Yes
`stories`	Yes
`next_offset`	No	Pass as `offset` to fetch the next page; null when there is no more.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two meaningful traits — the result is read-only and it returns compact rather than full data — but it says nothing about pagination behavior, total counts, or whether results are scoped by permissions.

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?

One front-loaded sentence describing the return contents and ordering, followed by a two-word safety marker ('Read-only.'). Nothing is redundant and the most important information comes first.

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 field-level return details need not be in the description, and this is a simple two-parameter list tool. The main gap is that the pagination parameters are neither documented in the schema nor explained in the description, which matters for a listing tool.

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?

Both parameters (limit and offset) have 0% schema description coverage, and the description never mentions pagination or what the bounds mean. The names and defaults are conventional enough to be guessed, but the description does not compensate for the undocumented schema.

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: it returns compact summaries of stored stories and enumerates exactly what each summary contains (title, ids, revision, latest update, turn and branch counts). The word 'compact' distinguishes it from heavier siblings like get_story_context or read_turns, but it never names those alternatives explicitly.

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 only implied: an agent can infer this is the overview/listing tool, reinforced by 'newest update first'. There is no explicit statement of when to choose it over get_story_context or read_turns, and no guidance on paging through large result sets.

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

Deploy Server