Skip to main content
Glama
Sign In
Claude Project History MCP Server

Claude Project History MCP Server

by MatthewDegtyar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Detect Workflow from Git Context

cph_detect_workflow
Read-onlyIdempotent

Detects the matching workflow for the current git branch, returning a match or a suggestion to create one when none exists.

Instructions

Detect which workflow matches the current git branch.

Call this if you don't have a workflow_id in CLAUDE.md yet, or if you're on an unfamiliar branch and want to know if a workflow already exists for it.

Returns either a matched workflow or a suggestion to create one.

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

Input Schema

NameRequiredDescriptionDefault
cwdNoWorking directory for git detection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate safe read operations. Description adds that it uses git context from the current branch and may suggest creating a workflow, providing useful behavioral context beyond annotations.

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?

Three short sentences: main purpose, usage conditions, and return info. No unnecessary words.

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?

Covers essential aspects for a simple read tool: when to use and return type. Lacks explicit statement that it reads the current git branch automatically, but implied.

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 covers the only parameter 'cwd' with description; main description does not add further explanation, meeting baseline for 100% schema coverage.

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?

Clear verb 'detect' and resource 'workflow from git context'. Distinguishes from sibling tools like cph_workflow_list by specifying git-branch-based detection.

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 states when to call: no workflow_id in CLAUDE.md or on unfamiliar branch, and mentions return values (match or suggestion).

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