Skip to main content
Glama
atakanelik34

Bilinc

by atakanelik34
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Show a memory's history

history
Read-onlyIdempotent

Trace how a memory key changed by inspecting its recorded changes newest first, including operations, times, reasons, sources, and before/after values.

Instructions

Show the recorded changes to one memory key, newest first.

    Read-only and free. Each entry has the operation (create, update,
    confirm, forget or delete), its time, the recorded reason and source,
    and the value before and after unless `values` is "none". A change
    made by a rollback keeps its create, update or delete operation and
    also carries `rollbackSnapshotId`.
    Values recorded before a memory was forgotten are not returned.
    `exists` is false when the key is not currently stored.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
limitNo
valuesNofull

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.11

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description goes far beyond by describing entry structure (operation, time, reason, source, before/after values), the rollbackSnapshotId behavior, the 'values: none' suppression, and that forgotten values are withheld. This is substantial behavioral context.

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?

Front-loaded with the core action and ordering, then structured detail. It is a bit list-like but every sentence conveys useful semantics; no filler.

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?

An output schema exists, so return format need not be explained, but the description still enriches it with field-level semantics and edge cases (rollback operations, forgotten values, exists=false). Complete for an agent to call correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the parameter burden. It explains the `values` parameter's semantics ("none" suppresses before/after values) and the `key` parameter's scope, compensating for the bare schema.

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 opens with 'Show the recorded changes to one memory key, newest first', a precise verb+resource+ordering statement. It is clearly distinguishable from siblings like diff or snapshot by specifying the auditable change log of a single key.

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?

It implicitly tells when to use the tool (auditing past changes to a key) but never names or contrasts with alternatives such as diff or snapshot. No explicit 'use this instead of X when Y' guidance.

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