Skip to main content
Glama

get_story_events

Retrieve a story's event history for a plan, newest first, with secret values masked and review or failure details when present.

Instructions

Return the story's event history, newest first, with secret values masked.

plan_name: the plan's name this story belongs to. story_key: the story's key within that plan's manifest. limit: how many of the newest events to return, clamped to 1..200; a non-integer uses the default of 50.

The events come from the plan's notification history in the namespace bound for the request. Each is {"seq", "ts", "event", "message"}. The story's own review_feedback, parked_reason, failure_reason and last_inconclusive_output_excerpt (masked, at most 4000 characters) are returned alongside them when the story carries them.

A story with no events is {"available": True, "events": []}. An unknown plan/story returns {"ok": False, "status": 404, "error": ...}.

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": {
      "plan_name": "<plan_name>",
      "story_key": "<story_key>"
    },
    "name": "get_story_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
plan_nameYes
story_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses newest-first ordering, secret masking, the namespace scoping of the underlying history, and the limit clamp to 1..200 with a default of 50 for non-integers. It stops short of stating permission or auth requirements and whether the result is paginated beyond the limit.

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?

Front-loaded with the one-line purpose, then a compact parameter block, then return semantics — a clean and scannable order with no filler. The return-shape paragraph is slightly redundant given an output schema exists, which keeps this from a 5.

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

Completeness5/5

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

Covers everything an agent needs for a 3-parameter read tool: what it returns, ordering, masking, the empty-events shape, and the 404 error path. The presence of an output schema lowers the bar for return documentation, and the description exceeds it anyway.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does: plan_name is scoped as the plan the story belongs to, story_key as the key within that plan's manifest, and limit gets clamping range, default, and non-integer fallback behavior. This is meaning the bare schema does not convey.

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 ('Return the story's event history') plus ordering and masking behavior, so the agent knows exactly what it gets. It does not differentiate itself from similar-sounding siblings such as get_story_log or get_story_journal, leaving the agent to infer which read tool to pick.

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

Usage Guidelines3/5

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

Usage is implied by the resource name and by the note about where events come from (the plan's notification history), but there is no explicit when-to-use or when-not-to-use guidance and no alternatives named. For a tool sitting in a cluster of story-read siblings, an explicit routing sentence is the missing piece.

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