Claude Project History MCP Server

by MatthewDegtyar

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Index Codebase Areas

cph_codebase_index

Idempotent

Instructions

Use this during plan mode to declare which parts of the codebase are relevant to the current workflow, what their responsibilities are, and their dependencies.

Each area is a path pattern (e.g. "src/auth/**") with an optional responsibility description and dependency list.

Upserts by workflow_id + path_pattern — safe to call multiple times.

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>",
      "areas": "<areas>"
    },
    "name": "cph_codebase_index"
  }
}

Input Schema

Name	Required	Description	Default
`workflow_id`	Yes
`areas`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jun 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description reinforces this with 'Upserts' and 'safe to call multiple times', and adds usage context. It does not contradict annotations. However, it omits details like return value or side effects, but the idempotency hint reduces the need for that.

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 concise with three short paragraphs, front-loading the key action. It could be slightly more streamlined (e.g., merging the first two sentences), but it remains focused and avoids unnecessary detail.

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's simplicity (no output schema, 2 required params), the description adequately covers what, when, and how to use it. It explains the upsert behavior and the structure of areas, making it complete enough for an agent to invoke correctly. A minor gap is lack of mention of response, but not critical.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage at the top level, the description compensates by explaining the areas parameter structure with an example ('src/auth/**') and clarifying that responsibility and dependencies are optional. It also explains the role of workflow_id via 'Upserts by workflow_id + path_pattern'. This adds meaningful context beyond the schema's minimal descriptions.

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 registers or updates file area ownership for a workflow, with a specific verb 'register or update' and resource 'file area ownership'. It distinguishes from sibling tools by focusing on codebase indexing for workflows and explicitly mentions 'plan mode', which is unique among the provided sibling list.

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

Usage Guidelines4/5

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

Explicitly says 'Use this during plan mode' and 'safe to call multiple times', providing clear context. However, it does not contrast with alternative tools like cph_context_sync, which might also deal with codebase context, so some ambiguity remains.

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