Skip to main content
Glama

Bucky

by com.buckybuild
OverviewDiscussionsAdmin

unsave Lot

unsaveLot
DestructiveIdempotent

Unsave one parcel by lotId. This also removes that saved lot from every folder. Projects are kept. Use preview=true first; this MCP tool does not provide Undo.

Input Schema

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

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the destructiveHint=true and idempotentHint=true annotations, the description discloses three important facts: the unsave cascades to every saved folder, projects are preserved, and the action is irreversible because there is no undo. As a result, the agent knows the extent of the side effects and the data that survives.

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?

It is three short sentences with no filler. The scope and cascade effect come first, then the recommended preview workflow. Every sentence adds new information.

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 destructive mutation with no output schema and annotations that already cover safety, the description supplies the missing impact details and the preview-first requirement. The only gap is post-condition behavior on invalid or already-unsaved lotIds, which the description does not cover.

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 67%: context and preview are already documented in the schema, so the description's only contribution is behavioral framing, not parameter meaning. The description does not explain what a lotId identifies or what happens when it is unknown or already unsaved, so a 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: 'Unsave one parcel by lotId', which makes it clear this is the inverse of saveLot. It also makes clear that the operation only affects the saved-lot entry, not the project, so an agent can distinguish it from saveToProject or removeSavedFolderItem.

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?

It states a concrete prerequisite workflow: 'Use preview=true first', and it states an exclusion: 'this MCP tool does not provide Undo'. This is strong guidance, though it never names or explicitly routes to a sibling such as removeSavedFolderItem when the agent only wants to detach from a folder.

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