Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

search_templates

Searches the template catalog by text, category and platform.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoText to search for in name, tagline and stack.
limitNoMaximum number of results (1-50, default 20).
limiteNoDEPRECATED alias of `limit`: it still works, but use `limit` (it will be removed in a future round, no date yet). Maximum number of results (1-50, default 20).
categoryNoCategory slug: web, mobile, desktop, saas, ecommerce, ia, landing, dashboards, juegos, api, herramientas.
platformNoPlatform slug: web, android, ios, windows, macos, linux, multiplataforma.
categoriaNoDEPRECATED alias of `category`: it still works, but use `category` (it will be removed in a future round, no date yet). Category slug: web, mobile, desktop, saas, ecommerce, ia, landing, dashboards, juegos, api, herramientas.
plataformaNoDEPRECATED alias of `platform`: it still works, but use `platform` (it will be removed in a future round, no date yet). Platform slug: web, android, ios, windows, macos, linux, multiplataforma.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesHow many templates match the filter (before trimming).
listedYesHow many go in `templates`.
templatesYesThe results, ordered by relevance and sales.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changed
    • changedInput schema / properties / categoria / description
      Previous value: -"ALIAS RETIRADO de `category`: sigue funcionando, pero usa `category` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `category`. Slug de categoría: web, mobile, desktop, saas, ecommerce, ia, landing, dashboards, juegos, api, herramientas."New value: +"DEPRECATED alias of `category`: it still works, but use `category` (it will be removed in a future round, no date yet). Category slug: web, mobile, desktop, saas, ecommerce, ia, landing, dashboards, juegos, api, herramientas."
    • changedInput schema / properties / category / description
      Previous value: -"Slug de categoría: web, mobile, desktop, saas, ecommerce, ia, landing, dashboards, juegos, api, herramientas."New value: +"Category slug: web, mobile, desktop, saas, ecommerce, ia, landing, dashboards, juegos, api, herramientas."
    • changedInput schema / properties / limit / description
      Previous value: -"Máximo de resultados (1-50, por defecto 20)."New value: +"Maximum number of results (1-50, default 20)."
    • changedInput schema / properties / limite / description
      Previous value: -"ALIAS RETIRADO de `limit`: sigue funcionando, pero usa `limit` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `limit`. Máximo de resultados (1-50, por defecto 20)."New value: +"DEPRECATED alias of `limit`: it still works, but use `limit` (it will be removed in a future round, no date yet). Maximum number of results (1-50, default 20)."
    • changedInput schema / properties / plataforma / description
      Previous value: -"ALIAS RETIRADO de `platform`: sigue funcionando, pero usa `platform` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `platform`. Slug de plataforma: web, android, ios, windows, macos, linux, multiplataforma."New value: +"DEPRECATED alias of `platform`: it still works, but use `platform` (it will be removed in a future round, no date yet). Platform slug: web, android, ios, windows, macos, linux, multiplataforma."
    • changedInput schema / properties / platform / description
      Previous value: -"Slug de plataforma: web, android, ios, windows, macos, linux, multiplataforma."New value: +"Platform slug: web, android, ios, windows, macos, linux, multiplataforma."
    • changedInput schema / properties / q / description
      Previous value: -"Texto a buscar en nombre, tagline y stack."New value: +"Text to search for in name, tagline and stack."
    • changedOutput schema / properties / listed / description
      Previous value: -"Cuántas van en `templates`."New value: +"How many go in `templates`."
    • changedOutput schema / properties / templates / description
      Previous value: -"Los resultados, ordenados por relevancia y ventas."New value: +"The results, ordered by relevance and sales."
    • changedOutput schema / properties / templates / items / properties / authorIsAgent / description
      Previous value: -"La vende una cuenta-agente, no una persona."New value: +"It is sold by an agent account, not a person."
    • changedOutput schema / properties / templates / items / properties / category / description
      Previous value: -"Slug de la categoría."New value: +"Slug of the category."
    • changedOutput schema / properties / templates / items / properties / compareAtUsdc / description
      Previous value: -"Precio tachado en USDC como NÚMERO (forma antigua), solo si es mayor que el vigente."New value: +"Struck-through price in USDC as a NUMBER (old form), only if it is higher than the current one."
    • changedOutput schema / properties / templates / items / properties / compareAtUsdcDecimal / description
      Previous value: -"El MISMO precio tachado como cadena decimal."New value: +"The SAME struck-through price as a decimal string."
    • changedOutput schema / properties / templates / items / properties / image / description
      Previous value: -"Dirección absoluta de la portada (o de la primera imagen de la galería)."New value: +"Absolute address of the cover image (or of the first gallery image)."
    • changedOutput schema / properties / templates / items / properties / name / description
      Previous value: -"Nombre, traducido al idioma del token."New value: +"Name, translated into the token's language."
    • changedOutput schema / properties / templates / items / properties / platforms / description
      Previous value: -"Slugs de las plataformas objetivo."New value: +"Slugs of the target platforms."
    • changedOutput schema / properties / templates / items / properties / priceUsdc / description
      Previous value: -"Precio vigente en USDC, como NÚMERO (forma antigua)."New value: +"Current price in USDC, as a NUMBER (old form)."
    • changedOutput schema / properties / templates / items / properties / priceUsdcDecimal / description
      Previous value: -"El MISMO precio como cadena decimal: la forma canónica."New value: +"The SAME price as a decimal string: the canonical form."
    • changedOutput schema / properties / templates / items / properties / rating / description
      Previous value: -"Valoración media (0 si no tiene reseñas)."New value: +"Average rating (0 if it has no reviews)."
    • changedOutput schema / properties / templates / items / properties / reviews / description
      Previous value: -"Cuántas reseñas tiene."New value: +"How many reviews it has."
    • changedOutput schema / properties / templates / items / properties / sales / description
      Previous value: -"Ventas acumuladas."New value: +"Accumulated sales."
    • changedOutput schema / properties / templates / items / properties / slug / description
      Previous value: -"Slug canónico de la plantilla."New value: +"Canonical slug of the template."
    • changedOutput schema / properties / templates / items / properties / stack / description
      Previous value: -"Tecnologías de la plantilla."New value: +"Technologies of the template."
    • changedOutput schema / properties / templates / items / properties / status / description
      Previous value: -"Madurez declarada: completo, en-progreso o mvp."New value: +"Declared maturity: completo, en-progreso or mvp."
    • changedOutput schema / properties / templates / items / properties / tagline / description
      Previous value: -"Frase corta de presentación."New value: +"Short pitch line."
    • changedOutput schema / properties / total / description
      Previous value: -"Cuántas plantillas cumplen el filtro (antes del recorte)."New value: +"How many templates match the filter (before trimming)."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must convey behavior on its own. It makes the read-only, search-like nature clear, but it does not disclose ordering, match semantics, pagination behavior, or any side effects beyond what a search implies. Acceptable for a simple search operation, but not richly transparent.

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 a single, front-loaded sentence with no filler. It conveys the action, the target resource, and the main filtering dimensions without wasting words.

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?

The detailed input schema and output schema reduce the burden on the description, and the core search behavior is clear. However, the description omits guidance on how this tool relates to sibling search and catalog tools, and it does not note the deprecated aliases except through the schema. It is minimally viable but has clear gaps.

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%, so the schema already documents every parameter. The description adds a light summary ('text, category and platform') but does not explain edge cases, aliases, or defaults; the schema handles those, 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 ('Searches'), a clear resource ('the template catalog'), and the available search criteria ('text, category and platform'). It is understandable on its own, though it does not explicitly differentiate from sibling search tools like search_help or my_templates.

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?

No usage guidance is provided: the description does not say when to prefer this tool over alternatives, when not to use it, or whether it covers public templates versus user-owned templates. Sibling tools such as search_help and my_templates exist, so an agent gets no help choosing among them.

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

All Bernuvia 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