Skip to main content
Glama
deenesjakoruzh
IgorGanapolsky

mcp-memory-gateway

by IgorGanapolsky
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

context_provenance

Read-only

Retrieve recent provenance events to track context history and maintain information continuity across sessions.

Instructions

Get recent context/provenance events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • scripts/contextfs.js:803-807 (handler)
    The core logic that retrieves provenance events by reading events.jsonl from the contextfs namespace.
    function getProvenance(limit = 50) {
  const eventsPath = path.join(CONTEXTFS_ROOT, NAMESPACES.provenance, 'events.jsonl');
  const events = readJsonl(eventsPath);
  return events.slice(-limit);
}
  • scripts/tool-registry.js:363-372 (registration)
    The tool definition and input schema registration.
    readOnlyTool({
  name: 'context_provenance',
  description: 'Get recent context/provenance events',
  inputSchema: {
    type: 'object',
    properties: {
      limit: { type: 'number' },
    },
  },
}),

Tool Definition Quality

C2.8/5.0
Behavior3/5

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

The description adds minimal behavioral context beyond the annotations. The annotation 'readOnlyHint: true' already indicates this is a safe read operation, and the description doesn't contradict this. It hints at retrieving 'recent' events, suggesting a time-based scope, but doesn't disclose details like rate limits, authentication needs, or what 'recent' means. With annotations covering safety, the description provides some value 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with a single sentence, 'Get recent context/provenance events', which is front-loaded and wastes no words. Every part of the sentence contributes to understanding the tool's purpose, making it efficient and easy to parse, though it could benefit from more detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a read operation with one parameter) and the presence of annotations but no output schema, the description is incomplete. It doesn't explain what 'context/provenance events' are, how they're returned, or the role of the 'limit' parameter. With annotations handling safety, the description should provide more context about behavior and outputs to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides no information about parameters, and with 0% schema description coverage for the single parameter 'limit', the schema alone offers no semantic context. Since the parameter count is low (1) but undocumented, the description fails to compensate for the coverage gap, leaving the agent unsure about how 'limit' affects the retrieval of events. This is below the baseline for minimal viability.

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

Purpose3/5

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

The description 'Get recent context/provenance events' clearly states the action (get) and resource (context/provenance events), making the purpose understandable. However, it lacks specificity about what these events entail and doesn't differentiate from sibling tools like 'describe_reliability_entity' or 'describe_semantic_entity', which might also retrieve contextual information. The description is functional but somewhat vague.

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

Usage Guidelines2/5

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 doesn't mention prerequisites, timing, or exclusions, and with many sibling tools like 'recall' or 'construct_context_pack' that might handle related data, the lack of differentiation leaves the agent without clear usage instructions. This omission reduces its effectiveness in tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IgorGanapolsky/mcp-memory-gateway'

If you have feedback or need assistance with the MCP directory API, please join our Discord server