Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

set_promo_code_active

Turns one of your discount codes on or off. Reversible; it deletes nothing and does not touch its history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId of the code (my_promo_codes gives it).
activeNotrue turns it on, false turns it off.
activoNoDEPRECATED alias of `active`: it still works, but use `active` (it will be removed in a future round, no date yet). true turns it on, false turns it off.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesAlways true: the change has been saved.
activeYesFINAL state of the code: on or off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / active / description
      Previous value: -"true lo enciende, false lo apaga."New value: +"true turns it on, false turns it off."
    • changedInput schema / properties / activo / description
      Previous value: -"ALIAS RETIRADO de `active`: sigue funcionando, pero usa `active` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `active`. true lo enciende, false lo apaga."New value: +"DEPRECATED alias of `active`: it still works, but use `active` (it will be removed in a future round, no date yet). true turns it on, false turns it off."
    • changedInput schema / properties / id / description
      Previous value: -"Id del código (lo da my_promo_codes)."New value: +"Id of the code (my_promo_codes gives it)."
    • changedOutput schema / properties / active / description
      Previous value: -"Estado FINAL del código: encendido o apagado."New value: +"FINAL state of the code: on or off."
    • changedOutput schema / properties / ok / description
      Previous value: -"Siempre true: el cambio se ha guardado."New value: +"Always true: the change has been saved."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the disclosure burden. It explicitly states the operation is reversible, deletes nothing, and preserves history, which is valuable behavioral context beyond the name. It does not discuss auth requirements or failure modes, but these are modest gaps for a simple toggle.

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 one tight, front-loaded sentence. Every clause adds value: the action, the ownership scope, and the non-destructive behavioral guarantees.

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

Completeness5/5

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

For a low-complexity tool with three parameters, full schema coverage, and an output schema, this description supplies the key behavioral facts an agent needs: what it does and that it is safe/reversible. Nothing essential is missing.

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 input schema already documents id, active, and activo with clear meanings. The description reinforces the boolean semantics ('on or off') but adds no new parameter-level meaning beyond 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 names a specific action, turning a discount code on or off, and identifies the resource it operates on. This clearly distinguishes it from siblings like create_promo_code and my_promo_codes, which create or list codes.

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 phrase 'one of your discount codes' clearly establishes when the tool applies: toggling the active state of an existing code. It gives clear context for use, though it does not explicitly name alternatives or list exclusion cases.

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