Skip to main content
Glama

add_items

Adds items to a Bring! shopping list, merging specifications when an item already exists.

Instructions

Add items. If an item is already on the list, the specifications are merged.

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": {
      "items": "<items>"
    },
    "name": "add_items"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-destructive, closed-world mutation, so the safety profile is covered. The description adds genuine value by disclosing merge-on-duplicate behavior, but it omits what a merge actually does to quantities, whether the list is auto-created, and whether a 100-item batch is atomic.

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?

Two short sentences, zero filler, with the core action front-loaded and the exception immediately following. Nothing could be removed without losing 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 two-parameter batch-add with null-safe annotations and no output schema, the definition is close to sufficient. The remaining gap is merge semantics detail and list-existence behavior, which matter more here than return values.

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 50%, so the description need not carry the full burden. Both parameters are documented in the schema itself, and the description adds only an indirect hint about the spec field via the merge rule; it says nothing about the optional list parameter or its default.

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?

"Add items" plus the duplicate-merge rule gives a specific verb and resource with one non-obvious behavioral qualifier. It does not distinguish itself from near-siblings such as add_staples or update_item, so the agent must infer the boundary from names alone.

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 statement, no prerequisites (e.g., whether the target list must already exist), and no alternative named. Only the duplicate-merge clause hints at when existing data favors this tool over update_item.

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