Skip to main content
Glama

Check a fruit story

get_fruit_story
Read-onlyIdempotent

Check an AI Fruit Story started with start_fruit_story: the step, 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 fruit 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_fruit_story"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
storyNo
storiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds useful context about the blocking wait of up to 40 seconds and the dual get/list mode. It does not discuss polling cadence, rate limits, or what happens when a story is still incomplete beyond 'the next step'.

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, no filler, front-loaded with the primary outcome and followed by the two mode modifiers (wait, no-id listing). Every clause carries information an agent needs.

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 return values need not be spelled out, and the description covers the prerequisite, the wait semantics, and the two calling modes. Minor gap: no guidance on how often to poll or when to prefer this over the legacy/story_video check tools, though the joint-label structure of the siblings makes the first inference safe.

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 coverage is 100% and every parameter is described there, so the baseline is 3. The description adds meaning beyond the schema by explaining that omitting id switches the tool into a listing mode, which reframes limit as a list-only parameter and id as a get-mode selector.

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

Purpose5/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 Fruit Story) and names the exact fields returned: the step, minutes left, and finished video link. It also names the prerequisite sibling start_fruit_story and distinguishes the no-id listing mode, so an agent can tell it apart from start_* and the legacy/story_video variants.

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?

Clear context: use after start_fruit_story to poll progress, use wait to block for up to 40 seconds, omit id to list recent stories. It does not explicitly exclude alternatives such as check_legacy_story or check_story_video, so routing among the three check_* families is left to inference.

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