Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

report_bug

Reports a platform bug to the team (10 characters minimum).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPath or screen where it happens (optional).
paginaNoDEPRECATED alias of `page`: it still works, but use `page` (it will be removed in a future round, no date yet). Path or screen where it happens (optional).
mensajeNoDEPRECATED alias of `message`: it still works, but use `message` (it will be removed in a future round, no date yet). Description of the bug (10-2000 characters).
messageNoDescription of the bug (10-2000 characters).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesAlways true: the report reached support.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / mensaje / description
      Previous value: -"ALIAS RETIRADO de `message`: sigue funcionando, pero usa `message` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `message`. Descripción del fallo (10-2000 caracteres)."New value: +"DEPRECATED alias of `message`: it still works, but use `message` (it will be removed in a future round, no date yet). Description of the bug (10-2000 characters)."
    • changedInput schema / properties / message / description
      Previous value: -"Descripción del fallo (10-2000 caracteres)."New value: +"Description of the bug (10-2000 characters)."
    • changedInput schema / properties / page / description
      Previous value: -"Ruta o pantalla donde ocurre (opcional)."New value: +"Path or screen where it happens (optional)."
    • changedInput schema / properties / pagina / description
      Previous value: -"ALIAS RETIRADO de `page`: sigue funcionando, pero usa `page` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `page`. Ruta o pantalla donde ocurre (opcional)."New value: +"DEPRECATED alias of `page`: it still works, but use `page` (it will be removed in a future round, no date yet). Path or screen where it happens (optional)."
    • changedOutput schema / properties / ok / description
      Previous value: -"Siempre true: el aviso llegó a soporte."New value: +"Always true: the report reached support."
  2. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description must carry behavioral weight. It says the report is sent to the team and imposes a 10-character minimum, but it does not disclose side effects, confirmation behavior, idempotency, or whether auth is required. This is thin for a mutating/reporting tool.

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?

Single sentence with the core action front-loaded. No filler; the min-length constraint is the only extra detail and is grammatically compact.

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 schema covers the four parameters and one-of requirement, and an output schema exists, so return values need not be explained. However, the description is too thin on when to select this tool and what behavior to expect beyond 'sends to team,' especially with 50+ siblings.

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% and every property has a description, including deprecation notes for the aliases. The description adds no parameter meaning beyond restating the 10-character minimum already present in the schema, so it stays at the high-coverage baseline of 3.

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 clear action ('Reports') and target ('platform bug') plus a recipient ('to the team'). This separates it from sibling communication tools such as open_dispute or reply_to_case, even without naming them.

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 when/why guidance is given. The description does not mention when a platform bug report is appropriate, how it differs from disputes or reviews, or any exclusions; it only states what the tool does.

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