Skip to main content
Glama

live_history

Read a block's history to see why it changed, including trigger and time.

Instructions

History of a block (e.g. why a blind moved: trigger and time). Read only.

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": {
      "block": "<block>"
    },
    "name": "live_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
blockYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It helpfully discloses that the operation is read-only, but it does not explain result limits, ordering, pagination, permissions, or what happens when no history exists for a block.

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 two short sentences with the core purpose front-loaded and no wasted wording. The parenthetical example is useful, though the definition is so terse that it leaves important gaps rather than being overlong.

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?

Given that there are no annotations, no output schema, and undocumented parameters, the description is not complete enough for reliable invocation. It should at least clarify the format of the 'block' parameter and the meaning or purpose of the 'page' parameter.

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 two parameters. The description implies that the 'block' parameter identifies the block whose history is returned, but it does not specify whether this is a name, ID, or path, and it says nothing about the optional 'page' parameter.

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 resource and action: retrieving the history of a block, with an example of what that history contains (trigger and time for a blind movement). It is clearly distinguishable from sibling tools like live_block or live_page, though it does not explicitly name alternatives.

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 guidance on when to use this tool versus alternatives such as live_block or live_status, and no conditions or prerequisites are given. The only context is that it returns history, leaving the agent to infer the appropriate use case.

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