Skip to main content
Glama
Sign In
RelayVault

RelayVault

by ranjitmani61
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

relayvault_list_history

Retrieves recent cross-model checkpoints and DAG lineage for a workspace, letting you inspect history and trace branch changes.

Instructions

List recent cross-model checkpoints and DAG lineage for a workspace.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "relayvault_list_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
branchNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "List" implies a non-mutating read, but the description does not confirm read-only safety, disclose ordering or pagination behavior implied by "recent" and the limit default, or mention any permission requirements.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is achieved partly by omitting information rather than by tight editing.

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?

An output schema exists so return values need not be explained, but for a three-parameter read tool with zero schema documentation and no annotations, the description should cover the branch filter, result capping, and the read-only nature. It leaves the agent guessing on how to use the tool beyond the required workspace_id.

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%, so the description must compensate and does not. It references only the workspace implicitly; the branch filter is completely unexplained and the limit parameter (default 10, presumably capping results) is never mentioned, leaving two of three parameters semantically opaque.

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 ("List") and a concrete resource ("recent cross-model checkpoints and DAG lineage") scoped to a workspace, which is enough to distinguish it from the clearly mutating siblings (commit_checkpoint, checkout_handoff). It stops short of explicitly contrasting itself with those siblings, and the terms "cross-model checkpoints" and "DAG lineage" are domain jargon left undefined.

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 when-to-use guidance at all: nothing says whether this should be called before commit_checkpoint, after checkout_handoff, or how to choose between them. The word "recent" hints at a browsing/inspection use case but no condition or exclusion is stated.

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

Deploy Server

Other Tools