Skip to main content
Glama
Sign In
Manthan

Manthan

by kidakaka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

audit_memory_lineage

Retrieves chronological Git commit history, agent author metadata, and diff audit trails for a memory artifact to verify provenance and review changes over time.

Instructions

Provenance & Time-Travel: retrieves chronological Git commit history, agent author metadata, and diff audit trail for a memory artifact.

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

Input Schema

NameRequiredDescriptionDefault
file_pathNoDirect file path of the memory file (relative or absolute)
memory_idNoID of the memory artifact to inspect (e.g. "mem_01j9x8k2m")
max_commitsNoMaximum number of commit history entries to return (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; 'retrieves' establishes a read-only, non-mutating character and it discloses what comes back (commit history, author metadata, diff trail). However it says nothing about behavior when the memory is untracked, what error surfaces for an invalid ID, or whether the operation is expensive on large histories.

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?

A single tight sentence with the purpose front-loaded in a label, then the concrete outputs. No filler, though the 'Provenance & Time-Travel:' prefix is slightly stylized and the enumerated payload could be framed more crisply.

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?

With no output schema, the description does list the returned elements, which covers the biggest gap. But for a 3-param inspection tool it omits ordering/pagination semantics, identifier-selection guidance, and failure modes, leaving meaningful holes an agent must guess at.

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%, so the schema already documents all three parameters, justifying the baseline 3. The description adds no guidance on the notable ambiguity that file_path and memory_id are both optional and required parameters is zero — an agent gets no help choosing between them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (retrieves) and concrete resources (chronological Git commit history, agent author metadata, diff audit trail) scoped to a memory artifact. It implicitly distinguishes itself from write-oriented siblings like commit_memory, but never names an alternative explicitly.

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?

'Provenance & Time-Travel' hints at the audit/inspection use case, but there is no explicit when-to-use statement, no exclusions (e.g., don't use for reading content — use recall_memory), and no mention of prerequisites such as the artifact needing to exist or be under Git tracking.

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