Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

set_template_active

Takes one of your templates out of the catalog (activa=false) or puts it back (activa=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.
activaNoDEPRECATED 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.
activeNofalse 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. 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."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does well: it discloses the immediate catalog effect, the human-review cycle for reactivation, and the impact on prior buyers. This is meaningful side-effect information beyond the name and schema, though it doesn't address possible state restrictions or reversibility of the review step.

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 concise sentences carry all essential behavioral information with no filler. The main toggle action is front-loaded, and the buyer caveat is a worthwhile second sentence.

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?

Given an output schema exists and the input schema is fully documented, the description provides enough context for an agent to call the tool correctly. It covers the toggle behavior, the review consequence, and the buyer-impact nuance, though it does not explicitly state any prerequisites or status constraints beyond ownership.

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 largely restates what the active/activa parameter descriptions already say, but it does add a small amount of interpretive context about the buyer's download being unaffected. It doesn't materially improve on the schema's already detailed parameter docs.

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 states a specific verb/resource pair: it toggles whether one of YOUR templates is in the catalog. It clearly distinguishes this from permanent retirement by noting that setting active=true puts it back and re-enters human review, and by specifying that prior buyers keep downloads either way.

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 makes the operational use case clear: set a template's active state to control catalog visibility. However, it never explicitly contrasts this tool with siblings like retire_template, submit_for_review, or resubmit_for_review, so when to choose this tool over those alternatives is left to inference.

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