Skip to main content
Glama
Sign In
ClaudeHistoryMCP

ClaudeHistoryMCP

by jhammant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_project_context

Retrieve recent sessions, key topics, common tools, and patterns to inject project context at session start.

Instructions

Get comprehensive context for a project: recent sessions, key topics, common tools, and patterns. Useful for session-start context injection.

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

Input Schema

NameRequiredDescriptionDefault
depthNoDetail level (default: normal)
projectNoProject name or path. Defaults to current working directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only lists what the tool returns, not whether it is read-only, whether it requires authentication, or any side effects. For a 'get' tool, it should explicitly state it does not modify anything, but that is absent.

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 two sentences, front-loaded with the main purpose and followed by a usage note. Every word earns its place; there is no redundancy or filler.

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?

Given the lack of annotations and output schema, the description should explain the return format and any behavioral details. It lists the content components but does not specify how 'depth' affects results, what 'recent' means, or whether the operation is safe/read-only. It is adequate but has clear gaps.

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?

The input schema provides 100% coverage, documenting both 'depth' (with enum and default) and 'project' (with description). The description adds no parameter-specific meaning beyond what the schema already states, so the baseline score of 3 is appropriate.

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's purpose: 'Get comprehensive context for a project' and enumerates the specific components (recent sessions, key topics, common tools, patterns). This distinguishes it from siblings like search_history or get_session_summary by emphasizing comprehensiveness and aggregation.

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?

It provides a clear usage context: 'Useful for session-start context injection.' This tells the agent when to invoke the tool. It does not explicitly mention alternatives or exclusions, but the context is sufficient.

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