Skip to main content
Glama

TeamShared

by io.github.xhad

Memory Session Append

memory_session_append

Append a turn to a working-memory session (self-healing).

When session_id has expired or was closed, a fresh session is opened automatically and the turn lands there; the response then carries the replacement session_id and reopened: true. Pass repo (and optionally github / topic) so reopen preserves workspace scope and updates the state pointer without a manual memory_state_set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoNoWorkspace slug. When set with an active bearer token, reopen self-healing updates the conversation/active-session pointer.
roleYesuser, assistant, tool, or system
topicNoSession topic used when reopening after expiry
githubNoGitHub owner/repo tag used when reopening a session
contentYesTurn content
session_idYesSession id from memory_session_open

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations are absent, so the description carries the full disclosure burden. It clearly explains the non-obvious self-healing behavior: expired or closed sessions trigger automatic reopening, the response contains the replacement session_id and reopened: true, and the state pointer is updated. This is exactly the kind of behavioral nuance an agent needs to anticipate.

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 compact and front-loaded: the core purpose appears first, followed by the self-healing edge case and the relevant optional parameter guidance. Every sentence earns its place, with no redundant restatement of the tool name or schema.

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 that an output schema exists to describe return values, the description fully covers the non-obvious behavior, the optional reopen parameters, and the relationship to memory_state_set. An agent has enough information to call this tool correctly in both normal and self-healing scenarios.

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

Parameters4/5

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

Schema coverage is 100%, establishing a baseline of 3. The description adds value beyond the schema by explaining why repo, github, and topic matter during reopen and how repo updates the state pointer, avoiding a manual memory_state_set. It does not deeply annotate every parameter, but it meaningfully supplements the 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 a specific action and resource: 'Append a turn to a working-memory session (self-healing).' The self-healing behavior and the contrast with sibling session tools like memory_session_open, memory_session_close, and memory_session_get make the tool's role unmistakable.

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

Usage Guidelines4/5

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

The description gives clear usage context: pass repo and optionally github/topic so a reopened session preserves workspace scope, and it explicitly contrasts with a manual memory_state_set call. It does not enumerate when to prefer this over session_open/ensure, but the append semantics and automatic-reopen behavior make the intended usage clear.

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

All TeamShared toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

With 104 tools across many domains (memory, work, projects, files, agents, context, strategic, ontology), the use of clear prefixes (memory_, work_, project_, file_, agent_run_, context_) makes most tools distinct. However, there are some potential confusions between memory_session_* vs memory_state_*, and memory_recall vs memory_think vs memory_assemble_context, though descriptions clarify their specific purposes. Aliases like memory_playbook_get for memory_procedure_get are explicit and reduce ambiguity.

Naming Consistency5/5

Tool names follow a highly consistent pattern: prefix_domain_action (e.g., file_create, work_update, memory_recall, agent_run_start). All use snake_case, with verbs consistently placed after the domain prefix. Even less common tools like account_brief and attention_snapshot fit the overall naming scheme, making the set predictable and easy to navigate.

Tool Count3/5

At 104 tools, this is an exceptionally large surface area, far exceeding the 25+ threshold that feels heavy. However, the server covers an extensive domain (organizational memory, work management, project tracking, file sharing, agent orchestration, and strategic planning), which justifies a large count. Still, the sheer number may overwhelm agents, and some tools could be consolidated (e.g., many memory_session_* and memory_state_* variants).

Completeness4/5

The tool surface is remarkably complete for its stated purpose, covering CRUD operations for files, work items, projects, and memory, plus lifecycle management for agents, sessions, and strategic plans. Minor gaps exist (e.g., no direct memory_item_get by ID, no section removal in projects), but agents can work around these using existing tools like memory_recall or work_create with parent_id. Overall, the set minimizes dead ends.

Resources