Skip to main content
Glama
basicmachines-co

basic-memory

by basicmachines-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cat

cat
Read-only

Print a note's content by title, permalink, or '/path' identifier, with optional section or line-range slicing to read only the part you need.

Instructions

Print a note's content. Accepts '/path' identifiers.

Input Schema

NameRequiredDescriptionDefault
projectNoProject name. Optional - the server resolves the default.
sectionNoHeading to slice to: "Decisions", path form "Auth/Decisions" to disambiguate by parent, or bracket form "Heading[1]" for the second duplicate heading. Cannot combine with start_line/end_line; the response's start_line/end_line support follow-up range reads.
end_lineNoLast line to include (inclusive). Defaults to the last line.
identifierYesNote title, permalink, memory:// URL, or '<project>/path' identifier (resolved exactly).
max_tokensNoApproximate token budget. Longer content is truncated at a section or paragraph boundary with an explicit ellipsis marker; the response carries truncated/continue_line for resuming.
project_idNoProject external_id (UUID); takes precedence over `project`.
start_lineNoFirst line to include (1-indexed, inclusive).
include_frontmatterNoInclude the YAML frontmatter block in `content`. Ignored for section/max_tokens reads — those slices never carry a frontmatter block. A start_line/end_line range combined with max_tokens addresses the full document (frontmatter included) and therefore requires include_frontmatter=True.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.24.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description itself adds little behavioral context beyond saying it prints content; it does not explain range reads, section slicing, truncation, or frontmatter handling.

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 two short sentences, front-loaded with the action and followed by the identifier form. There is no filler or repetition.

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

Completeness3/5

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

The tool has rich schema coverage, an output schema, and clear annotations, so the short description is not required to explain return values or parameter details. Still, for a read tool with several close siblings, the description omits enough selection guidance to be only minimally complete.

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%, so the schema already documents identifier, section, start_line, end_line, max_tokens, include_frontmatter, project, and project_id. The description only reiterates the "<project>/path" identifier form, 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: "Print a note's content." It also names the accepted identifier form. However, it does not distinguish this tool from overlapping siblings such as read_note, view_note, or read_content.

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?

The description gives only the accepted identifier syntax, not when to use this tool versus alternatives. There is no guidance about when to prefer cat over read_note, view_note, read_content, or bm_read.

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