Skip to main content
Glama
phasespace-labs

palinode

by phasespace-labs
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

palinode_read

Read-onlyIdempotent

Retrieve a memory file's full content after listing or searching. Use tier options to get an abstract, overview, or full body, and optionally include frontmatter.

Instructions

Read the full contents of a memory file. Use after palinode_list or palinode_search to see the complete content of a specific file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNoIf true, the response includes parsed frontmatter alongside the body. Default false (body only) to match prior behavior.
tierNoHow much of the file to return. 'abstract' is the summary line (~300 chars) — enough to judge relevance; 'overview' is frontmatter plus the head of the body; 'full' is the whole file. Omit for 'full'.
file_pathYesRelative path to the memory file (e.g., 'people/alice.md', 'projects/palinode-status.md')

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.16.0
    • addedInput schema / properties / tier
      Added value: +{
+  "description": "How much of the file to return. 'abstract' is the summary line (~300 chars) — enough to judge relevance; 'overview' is frontmatter plus the head of the body; 'full' is the whole file. Omit for 'full'.",
+  "enum": [
+    "abstract",
+    "overview",
+    "full"
+  ],
+  "type": "string"
+}
  2. First observedv0.9.5

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds workflow context and the full-content behavior, but no additional side-effect or error information; the strong annotations lower the burden and the description meets it without adding extra behavioral detail.

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, front-loaded with the core operation, then the practical intended usage. No wasted words and no repetition of schema details.

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?

For a read-only, idempotent file reader, the description plus fully described schema covers the workflow, parameters, and output-shaping options (tier, meta). No essential information is missing for an agent to call it correctly.

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 each parameter (file_path, meta, tier) already has a meaningful schema description. The tool description adds little beyond 'complete content' and the workflow, so the schema carries the semantic weight as expected.

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 names the action ('Read'), the resource ('a memory file'), and the scope ('full contents' / 'complete content of a specific file'). It also distinguishes the tool from siblings by positioning it after palinode_list or palinode_search.

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 explicitly states when to use the tool: after palinode_list or palinode_search, to retrieve complete content of a specific file. This gives the agent a clear workflow and differentiates read from list/search, which are the main alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/phasespace-labs/palinode'

If you have feedback or need assistance with the MCP directory API, please join our Discord server