Skip to main content
Glama
Sign In

Bucky

by com.buckybuild
OverviewDiscussionsAdmin

remove Saved Folder Item

removeSavedFolderItem
Idempotent

Remove exactly one saved lot or project from a private folder. Pass folderId and target with savedLotId or projectId. The lot stays saved and the project is kept. Use preview=true first.

Input Schema

NameRequiredDescriptionDefault
targetYes
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: -[
-  "folderId",
-  "target",
-  "context",
-  "llm_model"
-]New value: +[
+  "folderId",
+  "target",
+  "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

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and idempotentHint=true; the description adds the crucial side-effect context that 'The lot stays saved and the project is kept,' which is exactly the behavioral detail annotations cannot express. It does not cover failure cases, such as what happens if the item is not in the folder or lacks permission.

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 tight sentences, front-loaded with the action and scope, then the parameter guidance, then the safety step. No filler.

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 mutation tool with no output schema, the description covers scope, parameters, side effects, and a preview path, which is close to complete. Remaining gaps are error/idempotency specifics and folder-membership preconditions.

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 only 50%, and folderId has no schema description at all, but the description compensates by explaining that 'target' is a discriminated object taking either savedLotId or projectId, which the schema alone conveys only structurally. This is meaningfully more than the schema states.

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?

Names a specific verb and resource ('Remove exactly one saved lot or project from a private folder') and the 'exactly one' scoping distinguishes it from bulk operations. It also implicitly separates itself from deleteSavedFolder by noting the item is merely detached from the folder, though it never names that sibling explicitly.

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?

'Use preview=true first' gives an explicit precondition for safe invocation, and the two target variants (savedLotId or projectId) tell the agent which branch of the union to use. It stops short of stating when to prefer deleteSavedFolder or unsaveLot instead.

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