Skip to main content
Glama

list_my_stories

Lists your crack.wrtn.ai stories and returns story IDs for use with other tools. Supports pagination with limit and cursor for follow-up actions.

Instructions

내 크랙 스토리 목록. storyId는 다른 도구에 넘길 ID.

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_my_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden yet discloses almost nothing: no mention of pagination (despite limit/cursor), result ordering, or authentication requirements. The one useful disclosure — that storyId is the handle to pass into other tools — concerns the return shape rather than behavior, and there is no output schema to cover the rest.

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?

Two very short sentences with the resource statement front-loaded and the return-value hint second; nothing is padded or repetitive. It is terse to the point of under-specification, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a filterable, paginated list tool with no annotations and no output schema, the description is missing pagination, ordering, auth, and any differentiation from list_story_drafts. Only the storyId hand-off hint is a genuine addition, which is not enough for the tool's complexity.

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% and the description adds no meaning to either parameter. It says nothing about what limit controls (default 20, max 30) or what cursor represents or how to obtain one, so an agent must guess pagination mechanics from the raw schema.

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

Purpose3/5

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

The description states the resource ("내 크랙 스토리 목록" – my crack story list), so an agent can tell it returns a collection of stories. However, it never names a verb explicitly and does not differentiate it from the sibling list_story_drafts, leaving the agent to infer that this covers published/final stories rather than drafts.

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 when-to-use guidance at all: nothing says when to call this versus list_story_drafts or get_story, nor any prerequisite such as being logged in. The only hint of a workflow is that storyId is meant to be passed to other tools, which is not a selection rule.

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