Skip to main content
Glama
Sign In
mcp-zip

mcp-zip

by nanodaniel69
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memoria_leer

Reads a complete memory file for a project, retrieving stored context like summaries, errors, decisions, implementation, or plans.

Instructions

Lee un archivo de memoria completo.

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": {
      "nombre": "<nombre>"
    },
    "name": "memoria_leer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nombreYesNombre del proyecto
tipo_archivoNoTipo de archivo a leer (resumen, errores, decisiones, implementacion, plan)resumen

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'reads a complete memory file' but does not mention side effects, permissions, rate limits, or return format (despite an output schema existing, the description adds no transparency).

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

Conciseness4/5

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

The description is a single short sentence, which is concise and front-loaded. However, it lacks essential details for a complete understanding, but still scores high for brevity.

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?

Given the simplicity of the tool (2 parameters, no nested objects, output schema exists), the description provides minimal context. It does not explain what 'completo' means or how the output is structured, but for a basic read operation it is adequate.

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 coverage is 100% and both parameters have clear descriptions in the schema. The description does not add additional meaning beyond the schema, 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 clearly states the verb 'lee' (reads) and the resource 'archivo de memoria' (memory file), so the basic purpose is clear. However, it does not differentiate from sibling tools like 'memoria_resumen' which might also read from memory, and 'completo' is ambiguous.

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?

No usage guidelines are provided. The description does not indicate when to use this tool over alternatives, nor does it give any prerequisites or contextual hints.

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