Claude Project History MCP Server

by MatthewDegtyar

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

List Blockers

cph_blocker_list

Read-onlyIdempotent

List blockers by workflow and status to track and resolve project obstacles.

Instructions

List blockers by workflow and/or status.

Call this when user asks about blockers. session_init already surfaces open blockers — don't duplicate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cph_blocker_list"
  }
}

Input Schema

Name	Required	Default
`workflow_id`	No
`status`	No	open
`limit`	No
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jun 13, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds the duplication warning about session_init but does not disclose other traits like pagination behavior or required scopes. It adds some value but is not rich.

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?

Two sentences, front-loaded with purpose. Every word earns its place. No wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list tool with 4 optional parameters and no output schema, the description omits pagination details (limit/offset) and response format. Adequate but missing information that would help the agent use the tool fully.

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 coverage is 0%; description only vaguely mentions 'by workflow and/or status' without detailing parameters like workflow_id (uuid), status (enum with default), limit, or offset. It does not meaningfully compensate for the lack of schema 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?

Description clearly states 'List blockers by workflow and/or status' with a specific verb and resource. It distinguishes from sibling tools like cph_blocker_create and cph_session_init by noting that session_init already surfaces open blockers.

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?

Explicitly says 'Call this when user asks about blockers' and warns 'session_init already surfaces open blockers — don't duplicate', providing clear when-to-use and when-not-to-use guidance.

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