Skip to main content
Glama

Revdoku

by com.revdoku
OverviewDiscussionsAdmin

Bucket Template List

bucket_template_list
Read-onlyIdempotent

List trusted static-file templates that can be imported into a new private bucket. Each template contains ready-to-serve files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoOptional account id from revdoku_status.accounts for this call only. Omit for the credential's default account. Client accounts require explicit Agency authorization; never infer an account from a bucket id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
templatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Optional account id from revdoku_status.accounts for this call only. Omit for the credential's default account. Client accounts require explicit Agency authorization; never infer an account from a bucket id.",
+  "type": "string"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to restate safety. It adds context about 'trusted' and 'ready-to-serve' files, but no further behavioral traits such as pagination, filtering, or auth scoping beyond what the schema already states. The description is transparent but not additive beyond the structured metadata.

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 short sentences, each earning its place. The core action 'list trusted static-file templates' is front-loaded, followed by the useful qualifier that templates contain ready-to-serve files. There is no filler or repetition.

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?

With an output schema present, annotations describing safety, and full schema coverage for account_id, the description supplies the remaining domain context: these templates are static-file templates meant for new private bucket import. It is complete for a simple listing tool, though it could briefly mention that results feed into bucket creation.

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?

The input schema has 100% description coverage for the only parameter, account_id, which fully explains optionality, defaulting, and authorization. The description adds no parameter-level meaning, but with full schema coverage the description does not need to compensate. Baseline 3 is appropriate.

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 and resource: 'List trusted static-file templates that can be imported into a new private bucket.' It clearly differentiates from siblings like bucket_create_from_template (which creates) and bucket_list (which lists buckets) by scoping to reusable template artifacts. No ambiguity remains about what this tool returns.

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 phrasing 'that can be imported into a new private bucket' gives clear usage context: this list is a precursor to creating a bucket from a template. It does not explicitly name the sibling tool bucket_create_from_template or state when NOT to use it, so it stops just short of a perfect score.

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
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