Skip to main content
Glama
nworks3d

thor-memory-bible

by nworks3d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

get

Read-onlyIdempotent

Retrieves a stored memory item by its ID as formatted JSON, optionally listing recent session firings. Reports clear errors for unknown, diverged, or unparsable IDs instead of blank replies.

Instructions

Code lane: shows one item whole, by id. Use lookup instead when the id is not already known. Read-only. Reports a plain, honest error - never a blank reply that could look like success - when the id is unknown, when the item is DIVERGED (more than one current head; read history, then use resolve), or when its stored body will not parse. With fired: true it also lists where the item fired recently in this session (when, and the command or file) - what a verdict is judged by. Replies with the item as formatted JSON (then the firings, when asked), or the error text.

Input Schema

NameRequiredDescriptionDefault
idYesThe id to show.
firedNotrue also shows where the item fired recently in THIS session (newest first, at most 10 firings): when, and the command or file it fired on. What an evaluation judges a verdict by.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.6.0
    • addedInput schema / properties / fired
      Added value: +{
+  "default": null,
+  "description": "true also shows where the item fired recently in THIS session (newest\nfirst, at most 10 firings): when, and the command or file it fired on.\nWhat an evaluation judges a verdict by.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description goes further and enumerates the exact failure modes (unknown id, DIVERGED state, unparseable stored body) and guarantees a plain error rather than a blank reply that could mask failure. It also explains what the 'fired' flag produces and why it matters.

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 the routing rule, and every sentence carries information. It is dense with parentheticals (DIVERGED explanation, fired explanation) which slightly slows parsing but nothing is 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?

No output schema exists, and the description compensates by describing the return payload (item as formatted JSON, then firings, or the error text). Combined with the error-mode disclosure, an agent has everything needed to call and interpret it.

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 both 'id' and 'fired' are already documented in the schema, including the description of what fired returns. The description largely restates the fired semantics and adds only the output ordering ('then the firings, when asked'), so the baseline 3 applies.

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 ('shows one item whole, by id') and immediately distinguishes itself from the sibling 'lookup' by id-knownness. An agent can pick between get and lookup without opening either 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?

Explicit routing rules: use 'lookup' when the id is not already known, and read 'history' then 'resolve' when the item is DIVERGED. Both the alternative tool and the selecting condition are named.

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