Skip to main content
Glama

update_item

Replace the quantity or detail of a named item on a Bring! shopping list, optionally in a specific list, to keep entries accurate.

Instructions

Replace the specification (quantity/detail) of an item on the list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "spec": "<spec>"
    },
    "name": "update_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoBring list name (default: the main list)
nameYes
specYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful behavioral nuance that 'Replace' overwrites the existing quantity/detail rather than appending, but it does not say what happens if the item is absent or whether the prior value is recoverable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the parenthetical clarifying 'spec' is well placed. It is arguably too terse for a mutation tool, but it is not padded or repetitive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three parameters, a 33% schema coverage, and no output schema, the description covers the core intent but leaves gaps on item-matching semantics and on failure behavior when the item is not on the list. Adequate to call, not sufficient to predict the outcome confidently.

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 only 33% – 'name' and 'spec' have no schema description, and only 'list' is documented in the schema. The description partially compensates by clarifying that 'spec' means quantity/detail, but it says nothing about how 'name' is matched (exact match? case sensitivity?) or what happens on ambiguity.

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 ('Replace') and resource ('the specification (quantity/detail) of an item on the list'), so an agent knows this mutates an existing item's spec value. It does not name or distinguish itself from siblings like add_items, complete_items, or remove_items, leaving the boundary between it and them implicit.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no alternative named. An agent must infer that this is for changing an existing item's spec rather than adding, completing, or removing items, and must infer the precondition that the item already exists on the list.

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