Skip to main content
Glama

Buscar en texto completo

buscar_texto_completo
Read-onlyIdempotent

Búsqueda por términos del HTML realmente indexado (sin inventar contenido), con fragmentos y temas; diferencia registros con texto local de solo metadatos.

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_texto_completo"
  }
}

Input Schema

NameRequiredDescriptionDefault
temaNoEtiqueta tematica opcional, tal como aparece en las clasificaciones del indice.
limiteNoNumero maximo de coincidencias, entre 1 y 10 (predeterminado: 5).
consultaYesPalabras significativas que se buscaran en el indice del contenido HTML publicado.
solo_htmlNoSi es true, restringe resultados a documentos cuyo HTML se indexo completamente.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / consulta / description
      Added value: +"Palabras significativas que se buscaran en el indice del contenido HTML publicado."
    • addedInput schema / properties / limite / description
      Added value: +"Numero maximo de coincidencias, entre 1 y 10 (predeterminado: 5)."
    • addedInput schema / properties / solo_html / description
      Added value: +"Si es true, restringe resultados a documentos cuyo HTML se indexo completamente."
    • addedInput schema / properties / tema / description
      Added value: +"Etiqueta tematica opcional, tal como aparece en las clasificaciones del indice."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description adds real context beyond them: results are grounded in the actually indexed HTML ('sin inventar contenido'), returns include snippets and topics, and records may be local-text or metadata-only. It does not address empty-result behavior or ranking.

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?

A single dense sentence with the core purpose front-loaded, followed by the return shape and the metadata-only distinction. No filler; every clause carries meaning, though the parenthetical is slightly compressed.

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 four-parameter, read-only search with no output schema, the description covers the search domain, the returned elements (snippets, topics), and the data-quality caveat. 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.

Parameters3/5

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

Schema coverage is 100%, so all four parameters are documented in the schema itself. The description lightly reinforces that searches run over indexed HTML content and that topics correspond to index classifications, but adds no syntax, format, or edge-case detail beyond the schema. Baseline 3 applies.

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: term search over the actually indexed HTML, returning snippets and topics. It also names a distinguishing behavior (records with local text vs. metadata-only). It never names a sibling such as buscar_conocimiento or buscar_apps, so differentiation is implied 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 Guidelines3/5

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

Usage is implied rather than stated: the scope is limited to indexed HTML content, and the note about metadata-only records signals when results may be thin. There is no explicit when-to-use vs. an alternative search tool, and no exclusions or prerequisites.

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.