Skip to main content
Glama
Sign In
sixty60-mcp

sixty60-mcp

by matogen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Remove from Sixty60 cart

sixty60_cart_remove
Destructive

Removes a product from the Sixty60 cart or reduces its quantity, matching by product ID or partial product name so you can correct cart contents.

Instructions

Remove a product from the cart, or reduce its quantity. Match by product id or by part of the product name.

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": "<product>"
    },
    "name": "sixty60_cart_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoWhich cart: "sixty-min" (60-minute delivery, default) or "one-day" (Checkers Hyper / next-day).
weightNoFor products sold by weight: the pack range in grams, e.g. "300-500". Only needed if there are several.
productYesProduct id or part of its name as it appears in the cart.
quantityNoHow many to remove. Omit to remove the line completely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, so the mutation risk is known. The description adds useful context that partial-name matching is allowed, which implies possible ambiguity, but it does not say what happens on no match or on multiple name matches, nor whether removal is reversible. Adequate, not rich.

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, zero filler, with the primary action front-loaded before the matching rule. Nothing repeats the schema or the annotations.

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?

All four parameters are documented in the schema and the destructive nature is annotated, so the basics are covered. However, for a destructive matching-by-name operation the definition is silent on the not-found / ambiguous-match outcome and on what the response contains, which leaves a real gap for an agent deciding whether to call 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?

Schema coverage is 100% and each parameter already carries a description, so the baseline is 3. The description still adds value by stating that 'product' accepts a partial name as it appears in the cart, which clarifies the flexibility and the fuzziness of that field beyond the schema wording.

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?

States a specific verb and resource ('Remove a product from the cart') plus a secondary mode ('or reduce its quantity'), and explains the matching key ('by product id or by part of the product name'). It is clearly distinct from sixty60_cart_add and sixty60_cart_clear, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the two described behaviors: omit quantity for full removal, supply quantity for a partial reduction. There is no explicit routing against siblings such as sixty60_cart_clear (whole-cart wipe) or sixty60_cart_add, and no stated preconditions like being logged in or the cart already containing the item.

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