Skip to main content
Glama

AiAkiv Memory

by com.aiakiv
OverviewDiscussionsAdmin

get_memory_content

Read-onlyIdempotent

Fetch the stored text of one event.

Use this when a summary from a search or lookup result lacks the detail
needed to answer. Do not use it to browse a topic; it takes one event id.

Read-only. Long bodies arrive in pieces: `content` is a slice and
`char_count` is the body's total length, so while `next_offset` is not null
the body is incomplete — call again with `offset=next_offset` and join the
pieces until `next_offset` is null. A partial body is not the whole text.

Args:
    event_id: `events.id` (`ev_...`) or `vector_id` (`vec_...`).
    include_raw: True fetches the full body from `storage_uri`; False
        returns metadata alone, which suits large files and test queries.
    offset: Start character of the slice (default 0). Pass the previous
        response's `next_offset` to continue.
    limit: Characters to return in this call (default 15000, max 30000).
        Larger values are clamped, because the transport drops oversized
        responses silently and paging is what avoids that.

Returns:
    `{event_id, found, summary, content, char_count, offset, returned_chars,
    next_offset, storage_uri, section_heading, domain, inline_meta}`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoCharacters to return in this call (default 15000, max 30000). Larger values are clamped, because the transport drops oversized responses silently and paging is what avoids that.
offsetNoStart character of the slice (default 0). Pass the previous response's `next_offset` to continue.
event_idYes`events.id` (`ev_...`) or `vector_id` (`vec_...`).
include_rawNoTrue fetches the full body from `storage_uri`; False returns metadata alone, which suits large files and test queries.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds valuable behavioral detail beyond that: paging semantics, partial-body incompleteness, silent transport drops for oversized responses, and the meaning of include_raw. This is exactly the kind of context an agent needs to invoke the tool correctly.

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?

The description is detailed but every sentence earns its place: purpose, usage boundary, paging behavior, parameter explanations, and return shape. It is front-loaded with the most important information and uses clear structure.

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?

Given the output schema, annotations, and a description covering usage, paging, parameter behavior, and return fields, nothing an agent needs to call this tool correctly is missing. It is fully self-sufficient.

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%, so the schema fully documents all four parameters. The description repeats the same parameter meanings without adding significant new semantics beyond what the schema already provides. Baseline 3 is appropriate.

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 a specific verb and resource: 'Fetch the stored text of one event.' It also clarifies the scope ('takes one event id') and distinguishes itself from browsing/search tools, making its purpose unmistakable even among many sibling tools.

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 states when to use it ('when a summary from a search or lookup result lacks the detail needed to answer') and when not to ('Do not use it to browse a topic; it takes one event id'). This gives an agent clear selection criteria without needing to inspect other tools.

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

All AiAkiv Memory toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources