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).
messageYesDescription 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
    • removedInput schema / allOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "required": [
-          "message"
-        ]
-      },
-      {
-        "required": [
-          "mensaje"
-        ]
-      }
-    ]
-  }
-]
    • removedInput schema / properties / mensaje
      Removed value: -{
-  "deprecated": true,
-  "description": "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).",
-  "type": "string"
-}
    • removedInput schema / properties / pagina
      Removed value: -{
-  "deprecated": true,
-  "description": "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).",
-  "type": "string"
-}
    • addedInput schema / required
      Added value: +[
+  "message"
+]
    • removedInput schema / x-bernuvia-aliases
      Removed value: -{
-  "message": "mensaje",
-  "page": "pagina"
-}
  2. 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."
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not say where the report goes, whether it needs authentication, whether it is rate-limited or acknowledged, or what happens after submission — significant gaps for a mutation tool with zero annotation coverage.

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 — efficient and appropriately sized. It is arguably too terse for the amount of unspecified behavior, but nothing in it is wasted.

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

Completeness2/5

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

The output schema exists, so return values need not be explained, and the schema fully covers both parameters. However, with no annotations and a mutation-style tool, the description omits any account of side effects, handling, or follow-up — it is not complete enough for confident invocation.

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 'page' and 'message' are documented in-schema), so the baseline is 3. The parenthetical '(10 characters minimum)' restates part of the schema's 10-2000 character rule without adding new meaning, so no credit above baseline.

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 and resource ('Reports a platform bug to the team'), so the intent is unambiguous. None of the ~55 sibling tools overlap with bug reporting (they are all cart, template, dispute, wallet or profile operations), so sibling differentiation is implicit rather than stated.

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?

The description gives no when-to-use context, no prerequisites, and no routing to alternatives such as search_help or reply_to_case. An agent knows what the tool does but not when it is the right call versus existing support paths.

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