Skip to main content
Glama
Sign In
murphy-mcp

murphy-mcp

by lucianomanetta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Checkpoints recorded for this workspace

list_checkpoints
Read-onlyIdempotent

Lists saved checkpoints for a workspace in newest-first order, enabling review or comparison of prior workspace states.

Instructions

Lists the checkpoints stored under the workspace, most recent first.

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": {
      "root": "<root>"
    },
    "name": "list_checkpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootYesAbsolute path to the workspace to observe. Use the project root the agent is working in.

Output Schema

NameRequiredDescriptionDefault
rootYes
checkpointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully carried by structured data. The description adds the ordering behavior (most recent first), which is genuinely useful context beyond annotations, but says nothing about result limits, pagination, or what happens when a workspace has no checkpoints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded with the operation and tail-loaded with the ordering guarantee. Nothing is redundant or padded.

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?

A one-parameter read tool with full schema coverage, an output schema, and rich annotations needs little prose, and this description covers purpose and ordering. The only meaningful gap is the absence of any routing hint among the three sibling tools.

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 coverage is 100% and the single "root" parameter already documents that it must be an absolute path to the workspace. The description's "under the workspace" phrasing is consistent with the schema but adds no syntax or format detail beyond it, so the baseline of 3 applies.

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 names a specific verb and resource ("Lists the checkpoints") plus the ordering guarantee ("most recent first"), so the operation is unambiguous. It does not differentiate itself from the sibling tool "checkpoint", leaving the agent to infer which one records versus retrieves checkpoints.

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 phrase "stored under the workspace" in the parameter schema, which tells the agent to pass its project root. There is no explicit when-to-use statement, no exclusion, and no mention of the sibling tools (checkpoint, evidence_since, check_claims) that an agent might otherwise choose.

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