Skip to main content
Glama
Sign In
sixty60-mcp

sixty60-mcp

by matogen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Add to Sixty60 cart

sixty60_cart_add

Adds a product to a real Sixty60 cart by product ID or search term, increasing quantity if it already exists; supports 60-minute and next-day carts.

Instructions

Add a product to the real Sixty60 cart. Pass a product id from sixty60_search for an exact match; a search term adds the top search result. If the product is already in the cart, the quantity is added to it.

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_add"
  }
}

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 (preferred) or search term.
quantityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already state idempotentHint=false and destructiveHint=false, and the description reinforces the non-idempotent behavior by explaining that an existing line's quantity is incremented. It adds no information about authentication requirements, whether a cart is auto-created, or what the call returns, so the behavioral gain over annotations is modest.

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 tight sentences with the core action front-loaded, followed by the resolution and merge rules in the order an agent needs them. No filler or restated title text.

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 four-parameter mutation tool with no output schema and only partial annotation coverage, the description covers the critical ambiguity (id vs. search term, quantity merging). Minor gaps remain: nothing about login/cart prerequisites or the 50-unit cap interaction, and mode/weight are left entirely to the schema.

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 75%, so the schema already documents mode and weight well. The description still adds real meaning beyond the schema by defining the fallback resolution order for `product` (exact id match preferred, otherwise the top search hit) and the additive quantity semantics, which the schema does not express.

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?

The description opens with a specific verb and resource: "Add a product to the real Sixty60 cart." The word "real" usefully signals that this mutates an actual cart rather than a preview, but it never explicitly contrasts with siblings such as sixty60_cart_remove or sixty60_cart_clear, so differentiation is only implicit in the verb.

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?

It gives clear usage context by pointing to sixty60_search as the source of product ids and explaining what happens if a search term is supplied instead (top result is added). It stops short of explicit when-not guidance, e.g. when to prefer sixty60_product lookup or when a cart must already exist.

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