Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

search_help

Searches Bernuvia's help center and returns the full article if you pass its slug. Use it BEFORE explaining how the platform works: do not invent rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoWhat you want to know (e.g. «how do I withdraw my money»).
articleNoSlug of a specific article to read it in full (instead of searching).
articuloNoDEPRECATED alias of `article`: it still works, but use `article` (it will be removed in a future round, no date yet). Slug of a specific article to read it in full (instead of searching).
consultaNoDEPRECATED alias of `query`: it still works, but use `query` (it will be removed in a future round, no date yet). What you want to know (e.g. «how do I withdraw my money»).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoArticle branch: its address in the help center.
noteNoSearch branch: what to do with these results.
slugNoArticle branch: its slug.
textNoArticle branch: the whole plain text, with the figures already resolved.
titleNoArticle branch: its title.
totalNoSearch branch: how many results go in `articles`.
summaryNoArticle branch: its summary.
articlesNoSearch branch: up to 5 articles, from the most relevant to the least.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • changedInput schema / properties / article / description
      Previous value: -"Slug de un artículo concreto para leerlo entero (en vez de buscar)."New value: +"Slug of a specific article to read it in full (instead of searching)."
    • changedInput schema / properties / articulo / description
      Previous value: -"ALIAS RETIRADO de `article`: sigue funcionando, pero usa `article` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `article`. Slug de un artículo concreto para leerlo entero (en vez de buscar)."New value: +"DEPRECATED alias of `article`: it still works, but use `article` (it will be removed in a future round, no date yet). Slug of a specific article to read it in full (instead of searching)."
    • changedInput schema / properties / consulta / description
      Previous value: -"ALIAS RETIRADO de `query`: sigue funcionando, pero usa `query` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `query`. Qué se quiere saber (p. ej. «cómo retiro mi dinero»)."New value: +"DEPRECATED alias of `query`: it still works, but use `query` (it will be removed in a future round, no date yet). What you want to know (e.g. «how do I withdraw my money»)."
    • changedInput schema / properties / query / description
      Previous value: -"Qué se quiere saber (p. ej. «cómo retiro mi dinero»)."New value: +"What you want to know (e.g. «how do I withdraw my money»)."
    • changedOutput schema / properties / articles / description
      Previous value: -"Rama de búsqueda: hasta 5 artículos, del más relevante al menos."New value: +"Search branch: up to 5 articles, from the most relevant to the least."
    • changedOutput schema / properties / articles / items / properties / slug / description
      Previous value: -"Slug del artículo (para volver a llamar con `articulo`)."New value: +"Slug of the article (to call again with `articulo`)."
    • changedOutput schema / properties / articles / items / properties / summary / description
      Previous value: -"Resumen con las cifras ya resueltas."New value: +"Summary with the figures already resolved."
    • changedOutput schema / properties / articles / items / properties / title / description
      Previous value: -"Título del artículo."New value: +"Title of the article."
    • changedOutput schema / properties / articles / items / properties / url / description
      Previous value: -"Dirección del artículo."New value: +"Address of the article."
    • changedOutput schema / properties / note / description
      Previous value: -"Rama de búsqueda: qué hacer con estos resultados."New value: +"Search branch: what to do with these results."
    • changedOutput schema / properties / slug / description
      Previous value: -"Rama de artículo: su slug."New value: +"Article branch: its slug."
    • changedOutput schema / properties / summary / description
      Previous value: -"Rama de artículo: su resumen."New value: +"Article branch: its summary."
    • changedOutput schema / properties / text / description
      Previous value: -"Rama de artículo: el texto plano entero, con las cifras ya resueltas."New value: +"Article branch: the whole plain text, with the figures already resolved."
    • changedOutput schema / properties / title / description
      Previous value: -"Rama de artículo: su título."New value: +"Article branch: its title."
    • changedOutput schema / properties / total / description
      Previous value: -"Rama de búsqueda: cuántos resultados van en `articles`."New value: +"Search branch: how many results go in `articles`."
    • changedOutput schema / properties / url / description
      Previous value: -"Rama de artículo: su dirección en el centro de ayuda."New value: +"Article branch: its address in the help center."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description is the sole source. It explains the tool can either search or return a full article by slug, and warns against inventing rules. However, it does not disclose details like pagination, result limits, or the exact structure of the response beyond 'returns the full article'.

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?

The description is a single, well-structured sentence that front-loads the core purpose and immediate usage rule. It is concise with no wasted words, though not as terse as it could be with two sentences.

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?

Given the complexity (4 parameters, deprecated aliases, output schema present), the description provides good usage guidance but leaves out behavioral details like what happens when query vs article is used, or how results are formatted. The presence of an output schema mitigates the need to describe return values, but the tool's dual-purpose nature could be clearer.

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

Parameters4/5

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

Schema coverage is 100%, with descriptions for each parameter. The tool description adds the important distinction that query is for searching and article is for getting a full article, which complements the schema. It also clarifies the deprecated aliases in the schema, but the main description adds modest value.

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 clearly states it searches the help center and returns articles, with a specific instruction to use it before explaining platform rules. It is distinct from other search-like siblings (e.g., search_templates) by focusing on help content, though it does not explicitly name those siblings.

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?

The description gives explicit guidance to use it before explaining platform rules ('do not invent rules'), implying it should be used to ground answers in official documentation. It does not explicitly list exclusions or alternatives, but the directive is clear enough for an agent to know when to invoke it.

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