Skip to main content
Glama
Sign In
Mnemograph

Mnemograph

by tm42
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_state_at

Retrieve the exact state of your knowledge graph at any past moment using a timestamp, relative time, or named reference.

Instructions

Get graph state at a specific point in time (event rewind)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "timestamp": "<timestamp>"
    },
    "name": "get_state_at"
  }
}

Input Schema

NameRequiredDescriptionDefault
timestampYesTime reference: ISO datetime (2025-01-15), relative (7 days ago), or named (yesterday, last week)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description bears full burden. It implies a read-only operation but does not explicitly state safety, side effects, or permissions beyond the verb 'get'.

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?

Single sentence, front-loaded with verb and resource, no wasted words.

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

Completeness4/5

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

With one parameter and no output schema, the description is sufficient for a simple tool. It could mention the return format but is not necessary.

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

Parameters4/5

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

Schema coverage is 100% and the description adds valuable examples ('ISO datetime, relative, or named') that clarify the timestamp format beyond the schema's description.

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 verb 'Get' and the resource 'graph state', and adds context with 'event rewind', distinguishing it from sibling tools like 'rewind' which likely modify state.

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 usage for viewing state at a point in time but lacks explicit guidance on when to use this versus alternatives like 'restore_state_at' or 'rewind', and no exclusions are provided.

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