Hipocampo MCP

quick_hipocampo_search

Búsqueda rápida en el Hipocampo (alias corto de search_hipocampo).

Es solo lectura — no modifica datos, no tiene efectos secundarios.
Comportamiento y salida idénticos a search_hipocampo.

Útil cuando el cliente MCP prefiera nombres de herramienta más cortos.
Para nombre descriptivo, usar search_hipocampo.

Args:
    query: Texto de búsqueda en lenguaje natural. Igual que
           search_hipocampo. Ej: "API REST en Python", "presupuesto".
    session_id: Opcional. Filtra resultados a una sesión específica.

Returns:
    Mismo formato que search_hipocampo: resultados como texto plano
    con scores de relevancia y metadatos.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`session_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explicitly states it is read-only, has no side effects, and produces identical behavior and output to search_hipocampo. This is strong behavioral disclosure for a presumably safe search tool. It does not detail pagination or error behavior, but the alias's identical-to-search_hipocampo promise covers that expectation.

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 well-structured with clear sections: purpose, read-only guarantee, alias relation, usage guidance, parameters, and return format. Every sentence adds value. Minor redundancy exists with the alias statement being repeated, but the text remains compact and scannable.

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 simple alias with 2 params, 1 required, and an output schema, the description fully covers what an agent needs: behavior, safety, parameters, return format, and usage guidance. The output schema exists, so return values need not be detailed further. The only minor gap is a precise definition of session_id semantics beyond 'filters results', but the alias relationship to search_hipocampo mitigates this.

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?

Schema description coverage is 0%, so the description must compensate. It explains query as natural-language search text with concrete examples, and session_id as an optional filter to a specific session. It could add more detail on session_id semantics, but the parameter meaning is clear and goes beyond the bare schema.

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 identifies this as a quick alias for search_hipocampo with read-only search behavior. It states the verb ('Búsqueda rápida') and resource ('Hipocampo'), and distinguishes it from the canonical sibling by noting it is an alias for shorter client names. However, a fully standalone definition would explain what the search does even if read without knowledge of search_hipocampo.

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?

The description explicitly says when to use this alias: when the MCP client prefers shorter tool names, and directs users to search_hipocampo for the descriptive name. This gives clear alternatives and selection criteria, fully satisfying the dimension.

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

All Hipocampo MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?