Skip to main content
Glama

get_story_log

Retrieve the tail of a story's log with secret values masked to inspect recent execution output and diagnose issues by plan and story key.

Instructions

Return the tail of the story's log 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. lines: tail length, clamped to 1..500; a non-integer uses the default.

A story with no readable log returns {"available": False, "lines": []}. 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_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNo
plan_nameYes
story_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses that secret values are masked, lines are clamped to 1..500 with a default for non-integers, and it specifies return shapes for no-log and unknown plan/story cases. It stops short of stating permissions or read-only status explicitly, but 'Return' strongly implies a read operation.

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?

The description is front-loaded with the purpose sentence, then uses compact labeled lines for parameters and return cases. It is well-structured and mostly free of waste, though the return-value details are partly redundant with the existing output schema.

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?

For a simple read tool with no annotations and 0% schema description coverage, the description provides purpose, full parameter meanings, masking behavior, clamping rules, and error/empty return semantics. The main missing piece is explicit differentiation from sibling story-inspection tools.

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. It defines all three parameters: plan_name as the plan's name, story_key as the key within that plan's manifest, and lines as the tail length with clamping and default behavior. This fully covers the parameter meanings.

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 states a specific verb and resource: 'Return the tail of the story's log'. It is clear what the tool does, but it does not explicitly differentiate itself from siblings like get_story_journal or get_story_events, leaving some ambiguity for selection.

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?

The description gives no explicit when-to-use or when-not-to-use guidance relative to alternatives. It implies usage through the purpose statement and parameter explanations, but an agent must infer when to choose this over other story-inspection tools.

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