Skip to main content
Glama

Hipocampo MCP

by io.github.carrasquelalex1
OverviewDiscussionsAdmin

search_code

Busca código fuente indexado en Hipocampo (RAG).

Similar a search_hipocampo pero filtra solo recuerdos de tipo
code_snippet y devuelve fragmentos de código real con
ubicación de archivo.

Args:
    query: Consulta en lenguaje natural.
    k: Número de resultados (default 5, max 20).
    language: Filtrar por lenguaje (php, javascript, python, sql, etc.).
              Vacío = todos los lenguajes.

Returns:
    Fragmentos de código relevantes con metadatos de archivo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNo
queryYes
languageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/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 discloses read-like behavior and output content, but does not mention side effects, permissions, or rate limits, which would be expected without annotations.

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 concise and well-structured with clear Args and Returns sections, containing no redundant or irrelevant information.

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?

The tool description is self-contained for a search operation, covering purpose, parameters, and return content. With an output schema present, the return explanation is sufficient, though a brief example or mention of result count could make it slightly more complete.

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

Parameters5/5

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

Although the schema properties lack descriptions, the Args section fully explains each parameter: query is natural language, k has default and max values, and language has a default meaning. This adds complete semantic meaning beyond the bare schema.

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?

Description clearly states the action ('Busca código fuente indexado') and resource (Hipocampo RAG), and explicitly distinguishes it from search_hipocampo by filtering code_snippet memories and returning real code fragments with file locations.

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?

Directly compares to search_hipocampo and explains the filtering difference, making it clear when this tool should be preferred for code-specific searches, though it does not explicitly mention when not to use it.

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

All Hipocampo MCP toolsInspect
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