Skip to main content
Glama
server-noonien

server-noonien

Official

Read History

read_history
Read-onlyIdempotent

Trace which operations wrote an entity and when, newest first, with timestamps, nodes, and kinds. Use it to tell recently confirmed facts from long-untouched ones.

Instructions

Show what wrote an entity and when: the operations that touched it, newest first, with their timestamp, node and kind. Use it to tell a fact confirmed yesterday from one nobody has touched in months, which no other tool answers — read_conflicts covers only contested elements, and the graph itself carries no dates. For the current state use open_nodes; for what changed in a window use read_changes.

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": {
      "entityNames": "<entityNames>"
    },
    "name": "read_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoThe most operations to return, 50 by default and at most 500
offsetNoHow many operations to skip before the page; omit for none
entityNamesYesThe entities to trace; a relation counts under both of its endpoints

Output Schema

NameRequiredDescriptionDefault
entriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds behavior annotations do not: results are ordered newest first and carry timestamp, node and kind, and it notes the graph itself carries no dates — the key reason this tool exists. Pagination behavior is left to the schema, which is acceptable given full schema coverage.

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?

Two tight sentences with the capability and ordering front-loaded, followed by the sibling routing. No filler, no restatement of the title or annotations.

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

Completeness5/5

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

With an output schema, full parameter documentation and read-only annotations, the description only needs to establish purpose, ordering and sibling routing — all present. An agent can select and call this correctly from the definition alone.

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 description coverage is 100%, and the description adds no parameter-level detail beyond it — entityNames including the 'relation counts under both endpoints' nuance and the limit/offset bounds all live in the schema. Baseline 3 is the right call when the schema does all the work.

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?

States a specific verb and resource ('Show what wrote an entity and when: the operations that touched it') plus output shape (newest first, timestamp, node, kind). It is clearly separable from read_changes, read_conflicts and open_nodes without opening any schema.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names when to use this tool (distinguishing a recently confirmed fact from a stale one) and routes to alternatives by condition: read_conflicts for contested elements, open_nodes for current state, read_changes for a time window. Exclusions and alternatives are both stated.

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