Skip to main content
Glama
Sign In
ClaudeHistoryMCP

ClaudeHistoryMCP

by jhammant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_patterns

Find recurring patterns in conversation history: common topics, frequent workflows, and repeated issues to inform future sessions.

Instructions

Discover recurring patterns in conversation history: common topics, frequent workflows, repeated issues.

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": "find_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoType of patterns to find (default: all)
projectNoLimit to a specific project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden, but it only states the purpose ('Discover recurring patterns') and does not mention whether the tool is read-only, what it returns, or any side effects. This is insufficient for a tool with no annotation safety profile.

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 a single concise sentence that front-loads the core action and examples, with no wasted words. It is appropriately sized for the tool's simplicity.

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?

Although the schema fully documents the two optional parameters and the purpose is clear, the description omits any mention of the output format or behavioral boundaries (e.g., scope of conversation history). Given the simplicity of the tool and no output schema, this is a notable gap.

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 coverage is 100% with descriptive parameter names and a clear enum, so the description adds no additional parameter meaning. The baseline score of 3 applies as the schema already handles parameter documentation.

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 uses the specific verb 'Discover' and resource 'conversation history', and lists concrete pattern types (topics, workflows, issues), making its purpose distinct from siblings like search_history or find_solutions.

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

Usage Guidelines3/5

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

The description implies a use case (finding recurring patterns) but does not provide explicit guidance on when to use this tool versus alternatives such as search_history or find_solutions. No exclusions or alternative recommendations are given.

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