Skip to main content
Glama

remove_items

Destructive

Delete one or more products from a Bring! shopping list, choosing the main list or a named list, so you can keep buy or recently bought lists accurate.

Instructions

Remove items from the list (to buy or recently bought).

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": {
      "names": "<names>"
    },
    "name": "remove_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoBring list name (default: the main list)
namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds no behavioral context beyond that: it doesn't say whether removal is permanent, what happens if a name isn't found, whether partial or duplicate matches are affected, or that up to 100 names are handled per call.

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 short sentence with the operation front-loaded and no filler. It is efficient, though the parenthetical is slightly ambiguous about whether it describes the list type or the item state.

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

Completeness2/5

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

For a destructive, two-parameter mutation with no output schema, the definition says nothing about return values, failure modes, or irreversibility. An agent could call it correctly in the happy path but has no basis for handling missing names or confirming results.

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

Parameters2/5

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

Schema coverage is 50%: only the optional "list" parameter carries a description (defaults to the main list), while "names" is documented nowhere. The description's phrase "items from the list" adds no meaning about whether names must exactly match existing entries or whether unknown names cause errors, so it fails to compensate for the gap.

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?

The description pairs a specific verb ("Remove") with a specific resource ("items") and scopes it to the shopping lists ("to buy or recently bought"), which is enough to distinguish it from add_items and complete_items. It stops short of naming a sibling or stating the boundary against complete_items, so it isn't a 5.

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 when-to-use guidance at all: nothing says whether to remove an item versus mark it complete, whether items can be removed from the recently-bought list, or what prerequisites exist. The agent must infer usage from the tool name alone.

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