Skip to main content
Glama

get_story

Retrieves the full editable configuration of a published story, including its prompt and starting message, by story ID.

Instructions

공개된(최신 버전) 스토리의 편집용 전체 설정. 프롬프트, 시작 설정(첫 메시지) 포함.

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": {
      "storyId": "<storyId>"
    },
    "name": "get_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
storyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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. It usefully discloses what is returned (prompt, first message, full editing settings), but says nothing about permissions, behavior when the story is missing, or whether the read is safe/non-mutating beyond the 'get' verb.

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 short, front-loaded sentences with no wasted wording. The key scoping detail (published/latest) and the returned contents are stated immediately.

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?

For a simple one-parameter getter with no output schema, the description covers what is returned, which is the main need. However, it leaves the sole parameter and error/permission behavior undocumented, so it is only adequate rather than complete.

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 single parameter storyId is never mentioned in the description. The agent gets no added meaning about what identifier is expected or its format, so the description fails to compensate for the coverage gap.

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 names a specific verb+resource (get the story) and scopes it precisely: the published/latest version's full editing settings, explicitly including the prompt and starting settings (first message). This implicitly distinguishes it from get_story_draft (draft vs published), though it never names the sibling.

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 explicit when-to-use guidance and no alternatives are named. The 'published (latest version)' qualifier hints at the draft/published distinction, but the agent must infer that get_story_draft is the alternative for drafts rather than being told.

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