Skip to main content
Glama

Buscar guias y articulos

buscar_conocimiento
Read-onlyIdempotent

Buscar artículos, guías e investigaciones de AppInitDev con sus URLs originales.

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": {
      "consulta": "<consulta>"
    },
    "name": "buscar_conocimiento"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNoCantidad maxima de documentos devueltos, entre 1 y 20 (predeterminado: 10).
consultaYesTerminos de busqueda de articulos, guias o investigaciones de AppInitDev.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / consulta / description
      Added value: +"Terminos de busqueda de articulos, guias o investigaciones de AppInitDev."
    • addedInput schema / properties / limite / description
      Added value: +"Cantidad maxima de documentos devueltos, entre 1 y 20 (predeterminado: 10)."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by stating that returned documents include their original URLs, but it does not mention result ordering, pagination behavior, or what happens when no matches are found.

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?

It is a single compact sentence with no wasted wording. The search scope and the URL-returning behavior are both front-loaded and immediately useful.

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 two-parameter search tool with rich annotations, full schema coverage, and no output schema, the description covers the essential purpose and the form of returned results. It leaves a minor gap by not routing the agent among the many sibling search tools.

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 description coverage is 100%, with both "consulta" and "limite" fully documented including bounds and default. The description adds no parameter-level details beyond the schema, so the baseline of 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 states a specific verb ("Buscar") and resource types ("artículos, guías e investigaciones de AppInitDev"), and notes that results include original URLs. It is clear what the tool does, but it does not distinguish itself from siblings such as buscar_texto_completo or obtener_articulo.

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?

The description implies that this is the tool for searching AppInitDev articles, guides, and research, but gives no explicit when-to-use guidance, prerequisites, or alternatives. It never explains when an agent should choose this over buscar_texto_completo, buscar_apps, or obtener_articulo.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.