Skip to main content
Glama
Sign In
mcp-zip

mcp-zip

by nanodaniel69
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memoria_buscar

Search through project memories using full-text queries to retrieve relevant information. Optionally filter results to only active entries.

Instructions

Busca entradas de memoria por texto 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>",
      "query": "<query>"
    },
    "name": "memoria_buscar"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTexto a buscar
nombreYesNombre del proyecto
solo_activosNoSi es True, solo busca en entradas no archivadas

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 convey behavior. It implies a read-only search but does not explicitly state non-destructiveness, performance characteristics, or what happens with no results. The return format is not described, though an output schema exists.

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 concise sentence that front-loads the purpose. It is efficiently worded, but could benefit from slight expansion without losing conciseness.

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

Completeness2/5

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

Given the presence of sibling tools and no output schema details in the description, the definition lacks context on when to search vs read/list, and omits behavioral traits like pagination or filtering behavior. Incomplete for a 3-parameter 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 parameters are well documented in the input schema. The description adds no additional semantic context beyond the schema (e.g., how 'query' is matched, case sensitivity). 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 it searches memory entries by full text (verb 'busca' + resource 'entradas de memoria' + method 'por texto completo'). It is distinct from sibling tools like 'memoria_leer' (read specific) and 'memoria_listar' (list all), but lacks nuance about scope.

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 (e.g., 'memoria_leer' or 'memoria_listar'). No when-to-use, when-not-to-use, or prerequisites are mentioned.

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