Skip to main content
Glama
Sign In
Texas Grocery MCP

Texas Grocery MCP

by mgwalkerjr95
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cart_remove

Destructive

Remove a product from the shopping cart by providing its product ID. Preview changes without confirmation, or confirm to execute the removal.

Instructions

Remove an item from the shopping cart.

Without confirm=true, returns a preview of the action. With confirm=true, executes the action.

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": {
      "product_id": "<product_id>"
    },
    "name": "cart_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
sku_idNoSKU ID if known (will be looked up from cart if not provided)
confirmNoSet to true to confirm the action
product_idYesProduct SKU/ID to remove

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true. The description adds the preview behavior before confirmation, which is useful contextual information beyond the annotation.

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?

Two sentences, no unnecessary words, and the key information is front-loaded. Every sentence adds value.

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?

Given the output schema exists and the parameter descriptions are clear, the description is sufficient. It covers the main functionality and the confirm mode, though it omits error handling or edge cases.

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%, so each parameter is already described in the schema. The description mentions the confirm behavior but does not add new semantic detail for parameters beyond what the schema provides.

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?

The description clearly states it removes an item from the shopping cart, using a specific verb and resource. It distinguishes from sibling tools like cart_add and cart_get by implying the removal action.

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?

The description explains the confirm parameter's two modes: preview without confirm and execution with confirm. It implicitly tells when to use the tool but does not explicitly mention when not to use it or alternatives.

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

Deploy Server

Other Tools