Skip to main content
Glama

complete_items

Marks Bring! shopping list items as bought, moving them to the recently bought section. Specify item names and optionally a list to check off purchases.

Instructions

Mark items as bought (they move to "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": "complete_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

B3.3/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-destructive, closed-world call; the description adds the genuinely useful consequence that items are relocated to "recently bought" rather than deleted. It does not cover edge behavior such as unknown item names, duplicates, or partial failures.

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?

One short sentence, front-loaded with the action and immediately followed by its effect; nothing is wasted or buried.

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?

For a two-parameter mutation with no output schema, the description covers the core outcome but leaves open what happens to names that don't match, whether completion is idempotent, and how `list` should be chosen. Adequate, not complete.

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?

With only 50% schema description coverage, the description needs to compensate and does not: the `names` array is undocumented in both places, and nothing explains matching semantics or what `list` defaults to beyond the schema's own note. Only "items" hints that names is a batch of item labels.

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 and resource ("Mark items as bought") and adds the resulting state, which separates it from add_items and remove_items at a glance. It stops short of explicitly naming a sibling, so it is clear but not fully differentiated.

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?

"Mark items as bought" implies the shopping-list completion scenario, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as remove_items for discarding an item. The agent must infer the routing decision itself.

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