Skip to main content
Glama

get_staples_list

Read-only

Retrieve the staple items that are automatically added to a Bring! shopping list when missing, so clients can inspect or manage the recurring staples list.

Instructions

Staple items that add_staples (and the weekly job) add when they're missing from the list.

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": "get_staples_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine context missing from structured fields — that this list is the source set consumed by add_staples and by a recurring weekly job — but says nothing about ordering, what an empty list means, or whether the weekly job mutates the list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words, but it is a fragment that leads with content rather than an action verb, so it is not front-loaded with the tool's function. Brevity here comes partly at the cost of clarity.

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?

With an output schema present, the return shape needn't be documented, and there are no parameters or auth concerns to explain, which lowers the bar considerably. Still, the definition never states that the tool returns the current staples list, leaving the core contract implicit for an agent that has not already inferred it.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics for the description to add. The description neither helps nor harms on this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase ('Staple items that add_staples ... add when they're missing') rather than a verb-led statement, so it never explicitly says the tool retrieves that list. It does convey the resource and ties it to the sibling add_staples, which distinguishes it somewhat from that write tool, but the getter framing is only inferred.

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: nothing says 'call this to inspect the staples list before adding or replacing it,' and no exclusions or alternatives (e.g., set_staples_list for changing it) are named. The only guidance is an implicit association with add_staples and an unexplained 'weekly job.'

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