Skip to main content
Glama
Sign In
mcp-memoria

mcp-memoria

by lucabaello1998
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

listar_fuentes

Lists indexed sources—files, tags, sizes, and indexing dates—plus an index summary so agents can confirm available memory before searching.

Instructions

Lista las fuentes indexadas (archivos, etiqueta, tamaño y fecha de indexado) y el resumen del índice. Sirve para saber qué memoria está disponible antes de buscar.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listar_fuentes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does describe the response contents (source files, label, size, indexing date, index summary) despite no output schema existing. It is silent on scale, ordering, and pagination behavior, and never states read-only status outright, though "Lista" strongly implies it.

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, zero waste: the first front-loads what is returned, the second gives the use case. Every clause earns its place and nothing is repeated from the schema or title.

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

Completeness4/5

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

For a simple, no-argument, read-only listing tool with no annotations and no output schema, the description covers purpose, return contents, and usage timing. It could be slightly more complete by noting result scale or ordering, but nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters (empty object, additionalProperties false), so there is nothing for the description to disambiguate. Baseline for a zero-parameter tool is 4.

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?

States a specific verb and resource ("Lista las fuentes indexadas") and enumerates the fields returned (archivos, etiqueta, tamaño, fecha de indexado) plus the index summary. It contrasts its role with searching ("antes de buscar") but never names the sibling tool it complements, so differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Sirve para saber qué memoria está disponible antes de buscar" gives a clear when-to-use context: reconnaissance prior to a search. There is no explicit when-not guidance or a named alternative, but for a zero-argument listing tool the selection context is unambiguous.

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