Skip to main content
Glama

Read Resource (memory_read_resource)

memory_read_resource
Read-only

Provides fallback handling when a resource read is invoked as an MCP tool, returning structured error details, categories, and suggested fixes for failed journal requests.

Instructions

Fallback handler for memory_read_resource when invoked as an MCP tool instead of a protocol resource read.

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_read_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
use_test_dbNo
aggregated_errorsNoDetails of individual errors in a multi-step operation

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv9.1.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties
      Added value: +{
      +  "aggregated_errors": {
      +    "description": "Details of individual errors in a multi-step operation",
      +    "items": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "message": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "message"
      +      ],
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "category": {
      +    "description": "Error category (validation, query, connection, internal)",
      +    "type": "string"
      +  },
      +  "code": {
      +    "description": "Error code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)",
      +    "type": "string"
      +  },
      +  "details": {
      +    "additionalProperties": {},
      +    "description": "Additional error context",
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  "error": {
      +    "description": "Human-readable error message",
      +    "type": "string"
      +  },
      +  "recoverable": {
      +    "description": "Whether the error is recoverable",
      +    "type": "boolean"
      +  },
      +  "suggestion": {
      +    "description": "Suggested fix for the error",
      +    "type": "string"
      +  },
      +  "use_test_db": {
      +    "type": "boolean"
      +  }
      +}
    • addedOutput schema / additionalProperties
      Added value: +{}
    • addedOutput schema / properties / aggregated_errors
      Added value: +{
      +  "description": "Details of individual errors in a multi-step operation",
      +  "items": {
      +    "additionalProperties": {},
      +    "properties": {
      +      "message": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "message"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / category
      Added value: +{
      +  "description": "Error category (validation, query, connection, internal)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / code
      Added value: +{
      +  "description": "Error code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / details
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Additional error context",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / error
      Added value: +{
      +  "description": "Human-readable error message",
      +  "type": "string"
      +}
    • addedOutput schema / properties / recoverable
      Added value: +{
      +  "description": "Whether the error is recoverable",
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "$schema": "https://json-schema.org/draft/2020-12/schema"
      -}
    • addedOutput schema / properties / suggestion
      Added value: +{
      +  "description": "Suggested fix for the error",
      +  "type": "string"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
  2. First observedv9.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of what is returned, error behavior, or how the fallback path differs from a normal resource read, despite the schema being full of error-shaped fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no wasted words, but the brevity reflects under-specification rather than efficiency. There is no structure to speak of beyond the one clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with eight parameters, nested objects, and an output schema, the description is far too thin. It does not explain the resource being read, the meaning of the error-oriented parameters, or how this fallback relates to the sibling read tools, leaving the agent to guess.

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 88%, so the schema already documents nearly all eight parameters. The description contributes no additional parameter meaning, which is acceptable at this coverage level but adds no value.

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

Purpose2/5

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

The description only says it is a 'fallback handler' for the tool when invoked as an MCP tool rather than a protocol resource read. It never states what the tool actually does (read a memory resource) or what resource is being read, so an agent cannot infer the operation from the text alone.

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

Usage Guidelines2/5

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

It gives one narrow invocation condition (called as a tool instead of a protocol resource read) but offers no guidance on when to prefer it over the many sibling read tools such as read_resource, mj_read_resource, or get_entry_by_id. No exclusions or alternatives are named.

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