Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

set_template_active

Takes one of your templates out of the catalog (active=false) or puts it back (active=true, and then it goes through human review again). Whoever already bought it keeps their download either way.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSlug of YOUR template.
activeYesfalse takes it out of the catalog (it stops being sold); true puts it back, and then it goes through human review again.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesAlways true: a refusal travels as an error.
noteYesWhat it means for whoever bought it and what to do now.
slugYesSlug of the template.
activeYesHow it ends up: true in the catalog, false out of it.
inReviewNoOnly when it goes back to the catalog: it goes through human review again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / allOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "required": [
-          "active"
-        ]
-      },
-      {
-        "required": [
-          "activa"
-        ]
-      }
-    ]
-  }
-]
    • removedInput schema / properties / activa
      Removed value: -{
-  "deprecated": true,
-  "description": "DEPRECATED alias of `active`: it still works, but use `active` (it will be removed in a future round, no date yet). false takes it out of the catalog (it stops being sold); true puts it back, and then it goes through human review again.",
-  "type": "boolean"
-}
    • changedInput schema / required
      Previous value: -[
-  "slug"
-]New value: +[
+  "slug",
+  "active"
+]
    • removedInput schema / x-bernuvia-aliases
      Removed value: -{
-  "active": "activa"
-}
  2. Changed8 schema fields changed
    • changedInput schema / properties / activa / 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`. false la quita del catálogo (deja de venderse); true la devuelve, y entonces vuelve a pasar por revisión humana."New value: +"DEPRECATED alias of `active`: it still works, but use `active` (it will be removed in a future round, no date yet). false takes it out of the catalog (it stops being sold); true puts it back, and then it goes through human review again."
    • changedInput schema / properties / active / description
      Previous value: -"false la quita del catálogo (deja de venderse); true la devuelve, y entonces vuelve a pasar por revisión humana."New value: +"false takes it out of the catalog (it stops being sold); true puts it back, and then it goes through human review again."
    • changedInput schema / properties / slug / description
      Previous value: -"Slug de TU plantilla."New value: +"Slug of YOUR template."
    • changedOutput schema / properties / active / description
      Previous value: -"Cómo queda: true en el catálogo, false fuera."New value: +"How it ends up: true in the catalog, false out of it."
    • changedOutput schema / properties / inReview / description
      Previous value: -"Solo al devolverla al catálogo: vuelve a pasar por revisión humana."New value: +"Only when it goes back to the catalog: it goes through human review again."
    • changedOutput schema / properties / note / description
      Previous value: -"Qué implica para quien la compró y qué toca ahora."New value: +"What it means for whoever bought it and what to do now."
    • changedOutput schema / properties / ok / description
      Previous value: -"Siempre true: una negativa viaja como error."New value: +"Always true: a refusal travels as an error."
    • changedOutput schema / properties / slug / description
      Previous value: -"Slug de la plantilla."New value: +"Slug of the template."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose real behavior: deactivation stops sales, reactivation triggers a repeat human review, and existing purchasers retain downloads. It omits permission/ownership requirements and any reversibility or rate-limit notes, but the mutation effects are well communicated.

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 toggle's effects and ending with the buyer-protection clause. No filler, and every clause carries distinct information.

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?

An output schema exists, so return values need not be explained, and the description covers both parameter effects plus buyer impact. Minor gaps remain around ownership/permission prerequisites for toggling someone's template.

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 both parameters are already fully documented in the schema, and the description largely restates them (including 'YOUR template'). Baseline 3 is appropriate when the schema does the heavy lifting and the description adds no new syntax or constraint detail.

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 (set ... active) and resource (template), and covers both directions of the toggle with concrete consequences: out of catalog vs. back with human review. An agent can distinguish this from retire_template or resubmit_for_review from the text alone.

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?

Explains the condition selecting each value of 'active' (false removes it from sale, true restores it via review), which is clear usage context. It does not explicitly name or exclude the adjacent siblings (retire_template, resubmit_for_review) that overlap with these effects, leaving the routing to be inferred.

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