Skip to main content
Glama

Check memory status

memory_status
Read-only

Use this when the user asks whether MemoryRouter is connected, which opaque vault binding is active, or how many memories/tokens the connected vault contains. Does not reveal the memory key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
storageYes
vaultRefYes
connectedYes
reflectionNoReflection debt for the connected vault. Fields are null when the debt probe is unavailable.
totalTokensYes
grantedScopesYes
pendingTokensNo
totalMemoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / pendingTokens
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / reflection
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Reflection debt for the connected vault. Fields are null when the debt probe is unavailable.",
      +  "properties": {
      +    "raw_unconsolidated_tokens": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "suggestion": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "threshold_tokens": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "tier2_unconsolidated_tokens": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "raw_unconsolidated_tokens",
      +    "tier2_unconsolidated_tokens",
      +    "threshold_tokens",
      +    "suggestion"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered structurally. The description's real added value is the disclosure that the memory key is never revealed, which is a meaningful security boundary. Beyond that it says nothing about behavior when MemoryRouter is not connected, so it adds only modest context over the annotations.

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?

Two sentences, zero padding, with the trigger conditions front-loaded and the secrecy constraint placed as a closing caveat. Every clause carries information an agent would not otherwise have.

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?

With no parameters, an output schema present, and read-only annotations, the definition covers nearly everything an agent needs to select and call this tool. The one remaining gap is the disconnected/error state, which the description leaves to the output schema.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description spends no words redundantly restating empty input, which is appropriate.

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?

The description enumerates exactly what the tool reports: connection state for MemoryRouter, the active opaque vault binding, and memory/token counts for the connected vault. That is specific enough to distinguish it from content-reading siblings like inspect_memory or search_memories, though the phrasing is trigger-oriented ("Use this when the user asks...") rather than a direct statement of what the tool returns.

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?

It gives concrete triggering conditions (user asks about connection status, active vault binding, or memory/token counts) and adds a negative boundary: it does not reveal the memory key. It stops short of naming an alternative for the cases it does not cover, so there is no explicit when-not-to-use routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources