Skip to main content
Glama

Bucky

by com.buckybuild
OverviewDiscussionsAdmin

rename Saved Folder

renameSavedFolder
Idempotent

Rename a private folder by folderId. Pass name and use preview=true first to inspect the request without writing.

Input Schema

NameRequiredDescriptionDefault
nameYes
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
previewNoUse true to inspect the request without writing.
folderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / llm_model
      Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "folderId",
-  "context",
-  "llm_model"
-]New value: +[
+  "name",
+  "folderId",
+  "context"
+]
  2. Changed2 schema fields changed
    • removedInput schema / properties / folderId / format
      Removed value: -"uuid"
    • changedInput schema / properties / folderId / pattern
      Previous value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"New value: +"^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$"
  3. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare the safety profile (not read-only, non-destructive, idempotent), and the description adds the dry-run preview workflow, which is genuinely useful. It does not disclose permissions required to rename, whether the old name is recoverable, or what happens to folder contents, so it adds only moderate value beyond annotations.

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 with no waste; the operation and its identifier are front-loaded, and the preview recommendation follows immediately.

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?

For a simple mutation with no output schema and three required parameters, the definition plus annotations cover the essentials: what changes, how to target it, and how to dry-run it safely. Minor gaps remain around permission requirements and the unexplained name length constraint.

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 coverage is 50%: context is fully documented in the schema and preview is described identically there, while name and folderId carry no schema descriptions. The description identifies folderId as the folder selector and reinforces preview, but adds nothing about name constraints (1-120 chars) or the analytics-only nature of context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Rename a private folder") and names the identifier (folderId), which is clearly distinct from createSavedFolder, deleteSavedFolder, and listSavedFolders by verb alone. It does not explicitly contrast with siblings, so it stops short of a 5.

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?

Gives actionable usage guidance: supply name, and call with preview=true first to inspect the request before writing. It does not state when to prefer an alternative tool or any preconditions (e.g. ownership of the folder), which keeps it below a 5.

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

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