Skip to main content
Glama
Sign In
hermind-mcp

hermind-mcp

by fungane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_get

Read-only

Retrieves a note's full text by ID, including older versions, so you can review stored memory content.

Instructions

Full text of one note by id, with older versions.

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": {
      "id": "<id>"
    },
    "name": "memory_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNote id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds one useful behavioral detail beyond that – the response includes older versions of the note – but says nothing about behavior for an unknown id, version ordering, or output format.

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?

A single short sentence with no wasted words, front-loading the return content (full text) and the selector (id).

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?

For a one-parameter read-only fetch with a fully documented schema and no output schema, the description covers what is returned and how it is selected. Only edge-case behavior (missing id, shape of the version history) is left unstated, which is minor at this complexity.

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% for the single id parameter, so the schema already documents it. The description reinforces that exactly one note is returned for that id, which is marginal added meaning; baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource: retrieves the full text of a single note identified by id, including older versions. It is clearly distinguishable from memory_list and memory_search by its single-note-by-id scope, though it never names those siblings explicitly.

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?

Usage is only implied by the phrase 'by id' – an agent can infer this is the tool for when a note id is already known, versus discovery tools like memory_search or memory_list. There is no explicit when-to-use/when-not guidance or mention of alternatives.

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