Skip to main content
Glama

Buscar aplicaciones

buscar_apps
Read-onlyIdempotent

Buscar aplicaciones del catálogo oficial público de AppInitDev, con enlaces a la fuente.

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

Input Schema

NameRequiredDescriptionDefault
limiteNoCantidad maxima de aplicaciones devueltas, entre 1 y 20 (predeterminado: 10).
consultaYesNombre, categoria o funcion de una app. Ejemplos: Vault Wallet, archivos, fotos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / consulta / description
      Added value: +"Nombre, categoria o funcion de una app. Ejemplos: Vault Wallet, archivos, fotos."
    • addedInput schema / properties / limite / description
      Added value: +"Cantidad maxima de aplicaciones devueltas, entre 1 y 20 (predeterminado: 10)."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds that the catalog is public/official and that results include links to the source, which is modest but real context. It says nothing about result ordering, matching behavior (name vs. category vs. function) or empty-result handling.

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?

A single front-loaded sentence with no filler, and the scope qualifier plus return hint are packed efficiently. It is arguably too terse for a search tool, but nothing is wasted.

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

Completeness3/5

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

With only 2 well-documented parameters and full annotations, the definition covers the essentials for invocation. However, since there is no output schema, the description should do more to characterize results (fields returned, ordering, whether it is a substring or semantic match), and it only mentions source links.

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%: both 'consulta' (with examples) and 'limite' (range 1-20, default 10) are fully documented in the schema. The description adds no extra meaning about parameter interpretation, so the baseline of 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 (buscar) and resource (aplicaciones del catálogo oficial público de AppInitDev), plus a hint about the returned payload (enlaces a la fuente). This lets an agent distinguish it from knowledge or full-text search siblings by scope, though no sibling is named explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are mentioned despite several search-like siblings (buscar_conocimiento, buscar_texto_completo, obtener_app). Usage is only implied by the phrase 'catálogo oficial público'.

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.