Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

reply_to_review

Publishes the builder's reply to a review (moderated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoBuilder reply (5-1000 characters). ONE time only.
textoNoDEPRECATED alias of `text`: it still works, but use `text` (it will be removed in a future round, no date yet). Builder reply (5-1000 characters). ONE time only.
resenaIdNoDEPRECATED alias of `reviewId`: it still works, but use `reviewId` (it will be removed in a future round, no date yet). Id of the review (from my_reviews).
reviewIdNoId of the review (from my_reviews).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesAlways true: the reply has been saved.
inModerationYesAlways true: the reply goes through moderation before it can be seen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / resenaId / description
      Previous value: -"ALIAS RETIRADO de `reviewId`: sigue funcionando, pero usa `reviewId` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `reviewId`. Id de la reseña (de my_reviews)."New value: +"DEPRECATED alias of `reviewId`: it still works, but use `reviewId` (it will be removed in a future round, no date yet). Id of the review (from my_reviews)."
    • changedInput schema / properties / reviewId / description
      Previous value: -"Id de la reseña (de my_reviews)."New value: +"Id of the review (from my_reviews)."
    • changedInput schema / properties / text / description
      Previous value: -"Respuesta del builder (5-1000 caracteres). UNA sola vez."New value: +"Builder reply (5-1000 characters). ONE time only."
    • changedInput schema / properties / texto / description
      Previous value: -"ALIAS RETIRADO de `text`: sigue funcionando, pero usa `text` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `text`. Respuesta del builder (5-1000 caracteres). UNA sola vez."New value: +"DEPRECATED alias of `text`: it still works, but use `text` (it will be removed in a future round, no date yet). Builder reply (5-1000 characters). ONE time only."
    • changedOutput schema / properties / inModeration / description
      Previous value: -"Siempre true: la respuesta pasa por moderación antes de verse."New value: +"Always true: the reply goes through moderation before it can be seen."
    • changedOutput schema / properties / ok / description
      Previous value: -"Siempre true: la respuesta se ha guardado."New value: +"Always true: the reply has been saved."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It does disclose a meaningful trait: the reply is 'moderated.' However, it does not mention the one-time-only nature, mutability, permissions, or what happens after moderation; those details are left to the schema and output schema.

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 sentence with no filler. The key verb, resource, and moderation context are front-loaded, making it easy to parse quickly.

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?

Combined with the fully documented schema and the presence of an output schema, the description covers the essential context: publishing, reply, review, and moderation. It does not elaborate on the moderation workflow, but for a low-complexity call the provided information is sufficient.

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 baseline is 3. The description adds no parameter semantics beyond indicating the reply text and review target; aliases, deprecation, and the character-length constraint are all already documented in the schema.

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?

The description uses a specific verb ('Publishes') and a specific resource ('reply to a review'), making the action concrete. It is immediately distinguishable from sibling reply_to_case because the target resource is a review, not a case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the usage context—a builder responding to a review—but does not explicitly state when to use this tool versus reply_to_case or any other alternative. It relies on the tool name and sibling list rather than giving direct routing guidance.

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