Skip to main content
Glama
Sign In
sixty60-mcp

sixty60-mcp

by matogen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Empty Sixty60 cart

sixty60_cart_clear
Destructive

Removes every item from one Checkers Sixty60 cart; specify mode to clear either the 60-minute delivery cart or the one-day cart.

Instructions

Remove every item from one cart.

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

Input Schema

NameRequiredDescriptionDefault
modeNoWhich cart: "sixty-min" (60-minute delivery, default) or "one-day" (Checkers Hyper / next-day).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

destructiveHint=true already tells the agent items will be destroyed, so the description's "remove every item" mostly restates that. It adds no context about irreversibility, whether an empty cart errors out, or any confirmation requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded with the verb and resource, with no filler. Its brevity is appropriate, though it leaves little room for routing guidance.

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?

For a zero-required-parameter destructive tool with a fully documented schema and a destructiveHint annotation, the essentials are covered. Still, an agent gets no guidance on which of the two carts it operates on by default or how it relates to the sibling remove tool.

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?

The single mode parameter is fully described in the schema, including the enum values and the sixty-min default, so the description needs to add nothing and adds nothing. Baseline 3 applies when schema coverage is 100%.

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?

"Remove every item from one cart" gives a specific verb (remove), resource (cart), and scope (every item), which distinguishes it in spirit from the item-level sixty60_cart_remove. It stops short of naming that sibling, so the differentiation is inferential rather than explicit.

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 statement of when to use this tool versus sixty60_cart_remove or sixty60_cart_add, and no conditions such as "use when you want to start over." The bulk-clear intent is only implied by the word "every."

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