Claude Project History MCP Server

Overview Schema Source Related Servers Discussions Admin

Attach Commit to Recent Decisions

cph_decision_attach_commit

Idempotent

Attaches commit hash and diff stat to recent decisions recorded within 30 minutes that lack a commit link, ensuring each decision is tied to its corresponding commit.

Instructions

Internal: Called by the post-commit git hook to link recent decisions to a commit.

Do NOT call this manually. The hook calls it automatically after every commit.

Attaches commit_hash and diff_stat to decisions recorded in the last 30 minutes that don't already have a commit attached.

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": {
      "workflow_id": "<workflow_id>",
      "commit_hash": "<commit_hash>"
    },
    "name": "cph_decision_attach_commit"
  }
}

Input Schema

Name	Required	Description
`workflow_id`	Yes
`commit_hash`	Yes
`diff_stat`	No	Structural summary only: '3 files changed, 45 insertions'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jun 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses that it attaches commit_hash and diff_stat to decisions recorded in the last 30 minutes without an existing commit. Annotations include idempotentHint, and the description aligns with that. It doesn't detail error conditions but is transparent about its internal nature.

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?

The description is concise with three clear sentences, front-loading the purpose and restriction. No unnecessary words or repetition.

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?

Given the tool is internal and has no output schema, the description sufficiently explains its effect and constraints (30-minute window, idempotency). It could mention what happens if workflow_id is invalid, but overall is complete for its context.

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 only 33% (diff_stat has a description). The tool description mentions attaching commit_hash and diff_stat but doesn't explain workflow_id. The schema provides types and required status, so the baseline is adequate but the description adds minimal value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to link recent decisions to a commit, called by a post-commit git hook. The verb 'attach' and resource 'commit' are specific, and it differentiates itself from sibling tools like cph_decision_record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs not to call manually and states the hook calls it automatically after every commit. This provides clear when-not-to-use guidance, though alternative manual methods are not mentioned.

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