Skip to main content
Glama
Sign In
mcp-zip

mcp-zip

by nanodaniel69
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memoria_iniciar

Create a new project with an organized memory structure to store and retrieve context efficiently.

Instructions

Crea un proyecto nuevo con la estructura de memoria.

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

Input Schema

NameRequiredDescriptionDefault
stackNoStack tecnológico opcional (ej: "Next.js + Prisma")
nombreYesNombre del proyecto (ej: "ferreteria")

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Without annotations, the description carries the full burden of behavioral disclosure. It only states it creates a project but does not mention side effects (e.g., overwriting existing projects), required permissions, or what 'estructura de memoria' entails, leaving significant behavioral ambiguity.

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 a single sentence that efficiently communicates the core purpose without any redundant wording. It is front-loaded and to the point.

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 tool has 2 parameters and an output schema (not shown but present), the description is minimally complete. However, it lacks context about the project initialization process, such as idempotency or effects on existing data, which would be helpful for an agent operating this tool.

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%, so the input schema already describes both parameters ('nombre' and 'stack'). The description adds no additional meaning beyond what the schema provides, achieving the baseline for parameter semantics.

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 clearly states the verb 'Crea' (creates) and the resource 'un proyecto nuevo con la estructura de memoria'. It distinguishes itself from sibling tools like 'memoria_archivar' or 'memoria_buscar' by focusing on initialization of a new project, which is a distinct operation.

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 guidance is provided on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description is too minimal to inform an agent about context-specific usage decisions.

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