Skip to main content
Glama

get_list

Read-only

Fetches a Bring! shopping list's current to-buy and recently purchased items, optionally by list name; defaults to the main list.

Instructions

Items to buy and recently bought items of a 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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoBring list name (default: the main list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that the description adds almost nothing: no mention of ordering, whether completed items are truncated, whether multiple lists can be fetched, or how the two item groups are separated in the response.

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?

It is a single short sentence with no padding, but it is under-specified rather than efficiently concise; leading with a verb such as "Get the items to buy and recently bought items" would cost no extra words and remove ambiguity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A one-parameter read tool is simple, but with no output schema the description is the only place to learn what the return looks like, and it gives just a loose content hint. Nothing tells the agent whether this is the right entry point versus list_lists or get_staples_list.

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 description coverage is 100% and the single "list" parameter is fully documented in the schema, including the default to the main list. The description's "of a list" adds no meaning beyond that, so the baseline of 3 applies.

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 phrase "Items to buy and recently bought items of a list" tells the agent what content comes back and implies retrieval, but it is a noun fragment with no verb and never states that this fetches/reads the list. It gives partial differentiation from siblings like list_lists and get_staples_list by describing the item categories, but the operation itself must be 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, no mention of when to prefer get_staples_list over this tool, and no stated prerequisites. The only scoping hint (default to the main list) lives in the schema, not the description.

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