Skip to main content
Glama

get_story_draft

Retrieves the full settings for a single story draft by draft ID, enabling AI clients to inspect draft configuration before editing or managing the draft.

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": {
      "draftId": "<draftId>"
    },
    "name": "get_story_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about this being a read-only lookup, what happens when the draftId does not exist, or who can access the draft (auth/ownership). Only the name implies retrieval; the phrase "전체 설정" adds no behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but shortness here reflects under-specification rather than economy: a single fragment with no verb and no structure. There is nothing to front-load because almost no information is present.

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 tool with one undocumented required parameter, no annotations, and no output schema, the description should at minimum state what is returned and how to obtain the ID. It does neither, and it omits any note that "전체 설정" may be a partial or configuration-oriented view rather than the full story body.

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% for the single required parameter draftId, so the description must compensate and does not: "하나의" only vaguely implies the ID identifies a single draft, with no format, source, or expected origin (e.g., from list_story_drafts).

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

Purpose2/5

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

"임시저장본 하나의 전체 설정" translates to "the full settings of one draft," which names the resource but hides the operation behind "설정" (settings/configuration) rather than stating a retrieval verb. It is a near-restatement of the name get_story_draft, and it is ambiguous whether this returns a draft's content or its metadata/configuration, so it does not clearly distinguish itself from get_story or list_story_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 tells the agent how this differs from get_story, list_story_drafts, or save_story_draft, nor when a draft ID should come from list_story_drafts. The agent must infer everything from the name alone.

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