Skip to main content
Glama
Sign In
Ragionex Memory MCP

Ragionex Memory MCP

Official
by ragionex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Check memory processing status

ragionex_memory_status
Read-onlyIdempotent

Check a record's processing status in the selected Vault and return processing, ready, or failed with public guidance. Use an accepted save's record ID.

Instructions

Check a record's processing status in the selected Vault. Requires read permission. Returns processing, ready, or failed and any public guidance. Use for an accepted save with a record ID. For a locally queued operation ID, use ragionex_memory_connection.

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": "ragionex_memory_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecord ID to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • changedInput schema / properties / id / description
      Previous value: -"Memory ID to check."New value: +"Record ID to check."
    • addedInput schema / properties / id / pattern
      Added value: +"^[A-Za-z0-9_]{1,14}$"
  2. First observedv0.5.1

TDQS

A4.5/5.0
Behavior4/5

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

It goes beyond the standard 'readOnlyHint' annotation by explicitly stating operational requirements ('Requires read permission') and detailing the specific content of the output ('Returns processing, ready, or failed and any public guidance').

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 definition is brief and efficient. The initial sentences define the function, while the subsequent sentence is a highly dense but logically structured comparison to sibling tools.

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 it is a single-parameter read operation with no output schema, the description is maximally complete. It covers purpose, operational prerequisites, response content, and selection criteria among siblings.

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?

Since schema description coverage is 100%, the schema already defines the parameter's purpose (Record ID). The description here merely confirms that purpose and does not add unique semantic constraints.

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 uses a specific verb ('Check') and clearly defines the resource ('record's processing status'). It achieves distinction by specifying it is used 'for an accepted save with a record ID.'

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?

It provides highly actionable guidance by defining exactly when to use it (accepted save) versus when to use an alternative sibling tool (`ragionex_memory_connection` for locally queued operations).

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