Skip to main content
Glama

set_staples_list

Destructive

Replace the entire staples list with a new set of items and quantities, enabling you to update or reset recurring shopping staples in Bring!.

Instructions

Replace the whole staples 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": {
      "items": "<items>"
    },
    "name": "set_staples_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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 destructiveHint=true and readOnlyHint=false, so the safety profile is carried by structured data. The phrase "Replace the whole" usefully confirms that existing items are discarded wholesale rather than merged, but the description says nothing about empty-list behavior, the 100-item cap, or validation failures.

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?

One short sentence, front-loaded with the verb and scope, with zero redundant wording. It is efficient but sits at the edge of under-specification rather than informative conciseness.

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?

An output schema exists, so return values need not be explained, and annotations cover destructiveness. However, for a whole-list destructive replacement the description should at minimum note that prior contents are lost and how an empty `items` array behaves — neither is present.

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?

Top-level schema description coverage is 0%, and the description adds nothing about the single `items` parameter — no format, no example, no note that an empty array clears the list. The nested NewItem schema does document `name` and `spec`, which keeps this at baseline rather than below it.

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 names a specific verb and resource ("Replace ... staples list") and the qualifier "whole" signals full overwrite rather than incremental addition, which implicitly separates it from add_staples. It does not name any sibling explicitly, so sibling differentiation is left to inference.

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 or when-not-to-use guidance. An agent must infer that this is for wholesale overwrite versus add_staples for incremental changes; the description neither states that choice nor mentions any prerequisites.

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