Skip to main content
Glama

Check a legacy story

get_legacy_story
Read-onlyIdempotent

Check an AI Legacy Story started with start_legacy_story: the step, the progress, the minutes left, and the finished video link. With wait true the call waits up to 40 seconds for the next step. Without an id it lists the user's latest legacy stories.

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": "get_legacy_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe story id from start_legacy_story
waitNoWait up to 40 seconds for the next step. Default false.
limitNoWithout an id: how many stories to list. Default 5.

Output Schema

NameRequiredDescriptionDefault
storyNo
storiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral detail beyond that: the 40-second blocking semantics of wait and the implicit list-mode fallback when no id is supplied. It stops short of describing failure states (story errored, id unknown) or polling cadence guidance.

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?

Two sentences, front-loaded with the purpose and the originating-tool reference, followed by the two mode/parameter behaviors. No filler, no restatement of the tool name or annotations.

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

Completeness4/5

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

An output schema exists, so the return shape need not be spelled out, and the description still summarizes it usefully. For a zero-required-parameter polling tool the definition is essentially complete; only error/terminal-state behavior is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: it explains that id and limit form two distinct operating modes rather than independent knobs, and reiterates the 40-second wait bound. This mode framing is the real value-add over per-field descriptions.

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 ('Check an AI Legacy Story') plus the concrete payload an agent gets back (step, progress, minutes left, video link), and ties itself to the originating start_legacy_story call. It does not differentiate itself from near-identically named siblings such as check_legacy_story or check_story_video, which an agent would likely hesitate between.

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

Usage Guidelines4/5

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

Gives clear conditional usage: pass an id to poll a specific story started elsewhere, omit the id to list the user's latest stories, and set wait true to block for the next step. No explicit when-not or named alternative for the ambiguous 'legacy' vs 'story_video' siblings, so the routing guidance is complete for internal modes but not against competitors.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources