Skip to main content
Glama

add_staples

Adds missing staple items to a Bring! shopping list, skipping any already present, with an optional list name defaulting to the main list.

Instructions

Add to the shopping list the staple items that aren't on it yet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_staples"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoBring list name (default: the main list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (which only say it writes and isn't destructive), the description discloses a real behavioral trait: it adds only the staples that are missing, so it is idempotent-ish and won't duplicate existing entries. It still doesn't say what happens when every staple is already present, or whether the returned result lists what was added.

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 sentence, front-loaded with the verb and the dedupe qualifier. Nothing extraneous and nothing 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 write tool with no output schema, the definition is serviceable but thin: it doesn't say where the staple set comes from, what a caller should expect if the target list already has all staples, or whether the list must pre-exist. The annotations cover safety, and the schema covers the parameter, so these gaps are the only real omissions.

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 100% and the single 'list' parameter is fully documented in the schema, including its default. The description adds no further meaning about the parameter (e.g., what happens if the named list doesn't exist), so the baseline 3 applies.

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: adding staple items to the shopping list. The qualifier "that aren't on it yet" separates it from add_items (arbitrary items) and set_staples_list (configuring which items are staples), though it doesn't name those siblings explicitly.

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?

Usage is implied: call this to bulk-populate a list with whatever the configured staples are. There is no explicit when-to-use versus add_items, no note about prerequisites (e.g., whether a staples list must already exist), and no mention of the default main list being targeted.

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