Claude Project History MCP Server

Overview Schema Source Related Servers Discussions Admin

Thinking Time Summary

cph_thinking_summary

Read-onlyIdempotent

Infers thinking-time breakdown for recent turns by measuring gaps between tool calls. Returns per-turn and aggregate stats to analyze Claude Code's extended thinking.

Instructions

Get inferred thinking-time breakdown for recent turns.

Claude Code's extended thinking is not directly observable. This tool infers thinking time from the gaps between tool calls:

Initial gap: time from user prompt to first tool use
Interleaved gaps: time between consecutive tool calls
Final gap: time from last tool to response

Returns per-turn breakdowns, aggregate stats, tool baselines, and a caveat explaining inference limitations.

Args:

session_id: Filter to a specific session (optional)
workflow_id: Filter to a specific workflow (optional)
limit: Number of recent turns to return (default 10)

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_thinking_summary"
  }
}

Input Schema

Name	Required	Description
`session_id`	No	Filter to specific session
`workflow_id`	No	Filter to specific workflow
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jun 13, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds behavioral context: inference from gaps, non-direct observability, and a caveat explaining inference limitations, which exceeds annotation coverage.

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?

Description is front-loaded with summary, followed by clear explanation of inference method and returns. Each sentence adds value; minor redundancy in Args section but overall efficient.

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?

No output schema, but description explains return types (per-turn breakdowns, aggregate stats, tool baselines, caveat). Input schema covers all parameters. Inference method is explained, providing sufficient context for correct usage.

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 67%, so baseline is 3. The description repeats parameter meanings from schema (e.g., 'Filter to a specific session') without adding new semantics beyond the inference context.

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 'Get inferred thinking-time breakdown for recent turns', specifying verb and resource. It distinguishes itself from sibling tools by focusing on thinking time inference, which is unique among the listed tools.

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?

Description explains how inference works (initial gap, interleaved gaps, final gap) and what is returned, providing clear context. However, it lacks explicit guidance on when to use this tool versus alternatives, though no direct sibling exists.

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