Skip to main content
Glama
Sign In
sixty60-mcp

sixty60-mcp

by matogen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Sixty60 delivery slots

sixty60_delivery_slots
Read-only

Retrieve the next available delivery slots for the current address, with options for 60-minute delivery or next-day service.

Instructions

Next available delivery slots for the current address.

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

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.3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful scope with 'current address' and 'next available', but it does not clarify prerequisites such as whether an address or login must be set, nor does it explain freshness or return behavior.

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?

The definition is a single, front-loaded sentence with no redundant wording. Every phrase contributes to scoping the tool, and there is no unnecessary structure.

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 simple read-only slots lookup with one optional schema-documented parameter and no output schema, the description is adequate but minimal. It leaves ambiguous what defines 'current address' and whether the sibling address tool must be used first, which matters for correct invocation.

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 description coverage is 100%, and the single optional 'mode' parameter is fully documented in the schema with its enum values. The description adds no parameter meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 clearly identifies the resource as 'Next available delivery slots' and scopes it to 'the current address'. It is specific enough to distinguish this from cart, order, and address-management siblings, though the verb is implicit 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 explicit guidance on when to use this tool, when not to use it, or how it relates to alternatives such as sixty60_addresses or sixty60_checkout_preview. Usage is only weakly implied by 'Next available delivery slots'.

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