Find what changed in a file or function by merging git history with memory events to reveal recent modifications.
Explain what changed in a file or function recently by cross-referencing git history with episodic memory events mentioning the same target.
repo_path: optional absolute path to the target repository.
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | 7d | |
| target | Yes | ||
| repo_path | No | ||
| max_commits | No |
Changes observed during successful MCP inspections.
v1.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses the core behavior (cross-referencing git history and episodic memory) but omits details like side effects (none implied), error conditions, performance impact, or dependencies. Adequate but lacks depth.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, highly concise. The first sentence conveys the main purpose, the second provides one parameter detail. However, it sacrifices clarity for brevity, making it insufficiently informative. Still, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 4 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return values, how cross-referencing works, or input constraints like target format. Users are left without enough context to use the tool effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, yet the description only briefly mentions repo_path. It does not explain target (format?), since (units?), or max_commits. The description adds minimal value beyond the schema, leaving users to guess parameter meanings.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Explain what changed in a file or function recently by cross-referencing git history with episodic memory events mentioning the same target.' It uses a specific verb (explain) and resource (changes), and the method (cross-referencing) distinguishes it from siblings like episodic_search or search_docs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or context for use. The only extra detail is a parameter note about repo_path, which is not enough to guide selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.