Skip to main content
Glama
Sign In

OnlyMCP

by com.only-mcp
OverviewDiscussionsAdmin

Read a memory file

memory_read
Read-only

Read one memory file by path, whole or a range of its lines: from is the first line (counted from 1) and lines how many; the answer then names the total number of lines of the file. Docs: https://only-mcp.com/docs/what-is-onlymcp#what-sits-behind-the-one-address

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": {
      "path": "<path>"
    },
    "name": "memory_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoFirst line to return, counted from 1. Default 1.
pathYesPath of the memory file, for example project/proj-x.md
linesNoHow many lines, 1 to 2000. Default: the rest of the file, at most 2000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
+  "description": "First line to return, counted from 1. Default 1.",
+  "type": "string"
+}
    • addedInput schema / properties / lines
      Added value: +{
+  "description": "How many lines, 1 to 2000. Default: the rest of the file, at most 2000.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/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 clear. The description adds useful behavior beyond annotations by explaining range semantics and that the response names the file's total line count.

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 one front-loaded sentence that explains the operation, range behavior, and return detail without filler. The documentation link is brief and does not disrupt the core definition.

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?

For a simple read-only tool with complete schema coverage and clear annotations, the description covers purpose, range behavior, and one return detail. It could say more about missing-file behavior, but nothing critical for correct invocation is missing.

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%, and the schema already documents path, from, and lines. The description reinforces the from/lines meanings but adds no syntax or default details beyond what the schema provides, so baseline 3 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 states a specific verb and resource: read one memory file by path, whole or a range of lines. It clearly scopes the operation to a single file, though it does not explicitly name sibling alternatives such as memory_search or list_memory.

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

Usage Guidelines3/5

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

Usage is implied: use this when you need the contents of one known memory file, optionally a line range. However, it does not explicitly say when to prefer this over memory_search, list_memory, or memory_tree.

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

All OnlyMCP toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources