Skip to main content
Glama

Revdoku

by com.revdoku

Bucket Env Set

bucket_env_set

Set a bucket's integration variables and/or secrets (requires write access to the bucket). variables (PUBLIC — embedded into the published site and visible to every visitor) REPLACES the entire public set, so call bucket_env_get first and include the entries you want to keep. secrets (SERVER-only, encrypted, never returned) is a PATCH: a non-empty value sets/replaces it, an empty string deletes it, and omitted secrets are left unchanged. Names must be UPPER_SNAKE_CASE. Never put a secret value in variables.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
secretsNoServer-only secrets. Patch: non-empty sets, empty string deletes, omitted kept. Never returned.
bucket_idYesRevdoku bucket id returned by bucket_list or bucket_get, for example bkt_...
variablesNoPublic values embedded into the published site. Replaces the full public set.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
secretsNo
bucket_idNo
variablesNo

TDQS

A4.8/5.0
Behavior5/5

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

The description richly discloses behaviors beyond the annotation hints: variables are PUBLIC and REPLACE the entire set, secrets are SERVER-only, encrypted, never returned, and use patch semantics (empty string deletes, omitted unchanged). It also warns 'Never put a secret value in variables.' This is exemplary behavioral transparency.

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?

Four dense sentences convey purpose, preconditions, parameter semantics, and a critical safety warning. Every sentence adds value, and the structure is front-loaded with the primary purpose followed by essential details. No wasted words.

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?

The description is complete for the tool's complexity: it covers permissions, replace-vs-patch semantics, naming conventions, secret handling, and a safety warning. With an output schema present, return values need no explanation. It is fully adequate for an agent to select and invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds essential semantics: variables replaces the full public set (requiring a prior get), secrets is a patch operation with empty-string deletion, and names must be UPPER_SNAKE_CASE. This goes far beyond the schema's basic field type descriptions.

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 clearly states the tool's function: 'Set a bucket's integration variables and/or secrets.' It identifies the specific verb ('set'), the resource ('bucket's integration variables and/or secrets'), and distinguishes itself from sibling tools like bucket_env_get (which reads rather than writes).

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 description provides strong usage context, noting write access is required and explicitly instructing to 'call bucket_env_get first and include the entries you want to keep' to avoid overwriting the public set. It does not explicitly name alternatives or state when not to use the tool, but the guidance is clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Revdoku toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but a few overlaps exist: bucket_file_move and bucket_file_rename both handle same-bucket renames/moves, and bucket_file_reorganize overlaps with copy/move operations. The detailed descriptions help clarify, but the boundaries aren't always obvious.

Naming Consistency4/5

The naming follows predictable patterns: bucket_<verb> for bucket-level actions, bucket_file_<verb> for file operations, bucket_publication_<verb> for publications, and website_preview_* for previews. Minor deviations like bucket_create_from_template, bucket_set_public_slug, and bucket_update_publication_access deviate slightly but remain readable.

Tool Count2/5

At 42 tools, the server is overweight for its scope. While the platform is feature-rich, many tools are narrowly specialized (e.g., bucket_publication_leads, bucket_lock_visibility_changes) and some are redundant (file_move vs file_rename vs file_reorganize), making the surface larger than necessary for an MCP server.

Completeness3/5

The tool set covers the full bucket lifecycle and most file operations, but there is no direct file delete tool (only via delete_missing in write_many or cross-bucket move soft-delete) and binary uploads are explicitly delegated to the CLI/REST. These are notable gaps for a complete file management workflow.

Resources