Skip to main content
Glama

Layerz

by cc.layerz.app
OverviewDiscussionsAdmin

List version history

layerz_history
Read-only

Returns the version history of a model, newest first: { current_revision_id, current_version_number, history_days, hidden_count, oldest_hidden_at, pinned_count, max_pinned_versions, versions: [{ revision_id, version_number, created_at, trigger_type, actor_user_id, label, conversation_id, pinned }] }. Each version is a full snapshot persisted at one mutation boundary; revision_id (sha256 of the snapshot) is stable while the model is unchanged. Versions older than the plan window are counted in hidden_count but not listed; pinned versions stay listed whatever their age. limit and since scope the list. With uid, returns instead that item's change events across the history: { uid, events: [{ revision_id, version_number, created_at, actor_user_id, trigger_type, status: added | removed | modified, fields?: [{ field, oldValue, newValue }], branches?: [{ id, display_name, status, fields? }] }] } — fields describes the base plan, branches the overlay cells a branch records over it (a write under branch_id or an import on a branch lands there, not in fields).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidNoItem UID: returns that item's change events instead of the version list.
limitNoMax versions returned (default 100; with `uid`, max versions scanned, default 50).
sinceNoISO timestamp lower bound on the version list (ignored with `uid`).
model_idNoTarget model UUID. Required for user-scoped API keys; validated against the bound model for model-scoped keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max number of versions to return (default 100, clamped to plan retention)."New value: +"Max versions returned (default 100; with `uid`, max versions scanned, default 50)."
    • changedInput schema / properties / model_id / description
      Previous value: -"Target model UUID. Required for user-scoped API keys; ignored (or validated against scope) for model-scoped keys."New value: +"Target model UUID. Required for user-scoped API keys; validated against the bound model for model-scoped keys."
    • changedInput schema / properties / since / description
      Previous value: -"ISO timestamp lower bound — only versions created at or after this time."New value: +"ISO timestamp lower bound on the version list (ignored with `uid`)."
    • addedInput schema / properties / uid
      Added value: +{
+  "description": "Item UID: returns that item's change events instead of the version list.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

With annotations covering read-only safety, the description adds substantial behavioral context: newest-first ordering, hidden versions counted but not listed, pinned versions always listed, snapshot semantics at mutation boundaries, and the distinct return shapes for list vs. event modes. It also explains how `fields` and `branches` relate to the base plan and overlay cells.

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 and the primary return shape, then explains exceptions and the alternate mode. It is dense but every sentence carries necessary information, especially given the absence of an output schema. The use of inline object notation is efficient but may be slightly hard to scan.

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?

For a tool with no output schema, the description compensates thoroughly by documenting the full return shape in both modes, the behavior of hidden and pinned versions, and the effect of each parameter. The only minor gap is the model_id requirement for user-scoped keys, which is covered in the schema. Overall, an agent has everything needed to invoke and interpret the result.

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

Parameters3/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. The description reiterates the effect of `limit` and `since` in the list mode and clarifies that `since` is ignored with `uid`, but this largely duplicates what the schema already states. No additional syntax or format details are provided beyond the schema.

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 clearly states the verb and resource: 'Returns the version history of a model, newest first.' It also explains the dual-mode behavior with `uid`, which is specific and useful. However, it never distinguishes this tool from siblings like `layerz_manage_version` or `layerz_diff`, so it falls short of the top score.

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?

No explicit when-to-use or when-not-to-use guidance is given. The description describes behavior modes (list vs. change events) but leaves the choice to the agent based on the `uid` parameter. There is no mention of alternatives or prerequisites.

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

All Layerz toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources