Skip to main content
Glama
Sign In

Bucky

by com.buckybuild
OverviewDiscussionsAdmin

create Saved Folder

createSavedFolder

Create a named private folder. A repeated create makes another folder. Use preview=true first and listSavedFolders to check an uncertain outcome before retrying.

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.

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",
-  "context",
-  "llm_model"
-]New value: +[
+  "name",
+  "context"
+]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false; the description adds the practical consequence — a repeated create produces a duplicate folder rather than updating — plus a safe dry-run path via preview. It leaves out auth/permission requirements and what happens on duplicate names, but it meaningfully extends the annotation set.

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?

Three short sentences, front-loaded with the action, then the duplicate-creation caveat, then the safe-retry procedure. No filler and nothing buried.

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 create tool with annotations and no output schema, the description covers the main risk (accidental duplicates) and the mitigation. It omits error behavior on duplicate names and permission requirements, which an agent would want before calling in a real workspace.

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

Parameters4/5

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

Schema coverage is 67%, so baseline is 3; the description earns an extra point by explaining why preview exists in workflow terms ('use preview=true first'), which goes beyond the schema's terse 'inspect the request without writing'. The name parameter's constraints (1-120 chars) and the context analytics parameter are left entirely to the schema.

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 ('Create a named private folder'), which is clearly distinct from renameSavedFolder, deleteSavedFolder, and addSavedFolderItem. It doesn't explicitly contrast with saveToProject or saveLot, which are the nearest ambiguous alternatives, so it stops short of full sibling differentiation.

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 concrete operational guidance: use preview=true first, and use listSavedFolders to verify an uncertain outcome before retrying. It names the sibling to consult and the situation that warrants it, though it doesn't say when not to use this tool versus other save mechanisms.

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