Bernuvia

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

Name	Required	Description	Default
`query`	No	What you want to know (e.g. «how do I withdraw my money»).
`article`	No	Slug of a specific article to read it in full (instead of searching).

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	Article branch: its address in the help center.
`note`	No	Search branch: what to do with these results.
`slug`	No	Article branch: its slug.
`text`	No	Article branch: the whole plain text, with the figures already resolved.
`title`	No	Article branch: its title.
`total`	No	Search branch: how many results go in `articles`.
`summary`	No	Article branch: its summary.
`articles`	No	Search branch: up to 5 articles, from the most relevant to the least.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 27, 2026

removedInput schema / properties / articulo

Removed value: -{
-  "deprecated": true,
-  "description": "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).",
-  "type": "string"
-}

removedInput schema / properties / consulta

Removed value: -{
-  "deprecated": true,
-  "description": "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»).",
-  "type": "string"
-}

removedInput schema / x-bernuvia-aliases

Removed value: -{
-  "article": "articulo",
-  "query": "consulta"
-}

changedOutput schema / properties / articles / items / properties / slug / description

Previous value: -"Slug of the article (to call again with `articulo`)."New value: +"Slug of the article (to call again with `article`)."

Changed16 schema fields changedSep 23, 2026

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."

First observedSep 23, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It usefully explains the two operating modes (search vs. full-article fetch by slug), but says nothing about auth requirements, rate limits, or result truncation. For a low-risk read tool this is tolerable, hence a middle score.

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?

Two tight sentences, front-loaded with the core action and followed by the operational directive. Every clause carries information; nothing is padding.

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?

With an output schema present, return values need not be described, and both parameters are fully documented in the schema. The description is complete for a simple read tool, missing only minor operational notes about limits or failure modes.

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%, so the baseline is 3, and the description genuinely adds meaning by explaining the interaction: passing a slug returns the full article instead of performing a search. This clarifies how the two parameters relate rather than merely restating them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (searches) and resource (Bernuvia's help center), and additionally names the second mode (full-article retrieval by slug). No sibling tool covers help content, so it is unambiguously distinguishable from the rest of the catalog.

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?

Gives an explicit directive on when to use it — 'BEFORE explaining how the platform works; do not invent rules' — which is a clear usage condition. It doesn't name an alternative tool, but none exists for this resource, so the guidance is adequate.

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

All Bernuvia tools Inspect

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

Need Help?