Skip to main content
Glama
Sign In
sixty60-mcp

sixty60-mcp

by matogen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Sixty60 delivery addresses

sixty60_addresses
Read-only

List saved delivery addresses on your Checkers Sixty60 account and switch the delivery address used in the Sixty60 app.

Instructions

Saved delivery addresses on the account. Switch address in the Sixty60 app.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

With readOnlyHint=true already supplied, the description adds that these are saved addresses and that switching happens in the app, which usefully implies this is a read-only retrieval. It does not describe return format, pagination, or authentication needs, so it adds only modest context beyond annotations.

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?

Two short sentences with no wasted words, though the second sentence is somewhat ambiguous and could be clearer about whether it is a limitation or an instruction.

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-parameter read-only tool, the description covers the basic resource but does not explicitly state that it returns a list of saved addresses or clarify the 'switch' note. It is adequate but leaves minor ambiguity.

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?

The tool has zero parameters, so there are no parameter semantics to explain; the baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as saved delivery addresses on the account, but it lacks a clear verb such as 'list' or 'get' and does not distinguish this tool from siblings like sixty60_delivery_slots. The second sentence about switching in the app adds ambiguity rather than a precise action.

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?

No guidance is given on when to use this tool versus alternatives, and the instruction to switch address in the Sixty60 app could even suggest this tool is not for switching. An agent must infer its role from the name alone.

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