Skip to main content
Glama

Framezone

by app.framezone
OverviewDiscussionsAdmin

Update wishlist item

update_wishlist_item
Idempotent

Update a wishlist item — mark it purchased or cancelled, change priority, price or notes. Purchased and cancelled items drop out of the active list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoProduct URL (http or https)
nameNoNew name
notesNoNotes — reasoning, alternatives considered, purchase trigger
statusNopending = still wanted · purchased = bought · cancelled = no longer wanted
item_idYesWishlist item ID
categoryNoCategory
currencyNo3-letter currency code of the prices, e.g. GBP
priorityNohigh | medium | low | waiting (waiting = wanted but gated on a trigger)
price_maxNoUpper price estimate
price_minNoLower price estimate
purchased_atNoPurchase date (Y-m-d). Defaults to today when status becomes purchased.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / currency
      Added value: +{
+  "description": "3-letter currency code of the prices, e.g. GBP",
+  "type": "string"
+}
    • changedInput schema / properties / url / description
      Previous value: -"Product URL"New value: +"Product URL (http or https)"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is mutating, idempotent, and non-destructive. The description adds a meaningful side effect beyond those annotations: purchased and cancelled items drop out of the active list. This gives the agent useful behavioral context without contradicting the 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?

A single compact sentence with no filler. It front-loads the action, lists the supported changes, and then states the most important side effect. Every clause earns its place.

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?

Together with the fully described schema and annotations, the description covers the primary use case, the mutating operations, and the key behavioral outcome of active-list removal. It does not enumerate every field, but those are already in the schema, so nothing critical is missing for correct invocation.

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 description coverage is 100%, so all 11 parameters are already documented. The description loosely references priority, price, notes, and status, but adds no format, validation, or dependency details beyond what the schema provides, so it remains at the baseline.

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 names a specific verb and resource ('Update a wishlist item') and enumerates the supported mutations: mark purchased/cancelled, change priority, price, or notes. This clearly distinguishes it from add_wishlist_item, list_wishlist, and other sibling update tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes clear this tool modifies an existing wishlist item, but it never explicitly contrasts it with add_wishlist_item or states when not to use it. Usage is implied by the tool name and resource rather than expressed as routing guidance.

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

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