Skip to main content
Glama

clear_grocery_list

Destructive
Empty the connected account's grocery list: every item and every
"Recipes on this list" entry (substitution rules stay) -- requires
Subscriber. Can't be undone; only do this when the human asked for it.

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

Input Schema

NameRequiredDescriptionDefault
session_tokenNoThe session token check_agent_connection returned for the connected account. Required, unless it's sent as an Authorization: Bearer header on the MCP request instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: irreversibility ('Can't be undone'), the subscription prerequisite, and — most usefully — that substitution rules survive the clear while list items and 'Recipes on this list' entries do not. It doesn't say what happens on an empty list or what the response looks like, but annotations already carry the destructive profile.

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 tight sentence with the scope up front, the preserved data parenthetical adjacent to what's deleted, and the prerequisite and caution trailing. No filler.

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 one-param destructive tool with no output schema, the definition covers scope, exceptions, prerequisite, and reversibility — everything needed to call it safely. Only marginal gaps remain, such as the empty-list case and result shape.

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?

Single optional session_token parameter with 100% schema description coverage, so the schema already explains it fully (including the Authorization: Bearer alternative). The description adds nothing param-specific, which is the correct baseline-3 outcome when the schema does the work.

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

Purpose5/5

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

Specific verb (empty) plus resource (grocery list) with explicit scope: every item and every 'Recipes on this list' entry. The parenthetical '(substitution rules stay)' precisely bounds what is NOT cleared, which lets an agent distinguish this from remove_grocery_list_item and remove_recipe_from_grocery_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear gating condition: 'only do this when the human asked for it,' which is exactly the right caution for a bulk destructive call and implies the narrower sibling tools for single removals. It also states 'requires Subscriber' as a prerequisite, though it does not name the alternative tools explicitly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources