sixty60-mcp

Finish Sixty60 login

sixty60_login_verify

Verify the SMS one-time PIN to complete Checkers Sixty60 login and save the session, which stays valid for about an hour, using the reference returned when login started.

Instructions

Verify the SMS one-time PIN and save the session (valid about an hour).

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": {
      "reference": "<reference>",
      "code": "<code>"
    },
    "name": "sixty60_login_verify"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	The numeric code from the SMS.
`reference`	Yes	Reference returned by sixty60_login_start.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the disclosure burden. It usefully states that a session is saved and lasts about an hour, but says nothing about failure behavior for an invalid or expired code, whether retries are permitted, or whether a prior session is replaced.

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?

A single tight sentence with no waste; the core action is front-loaded and the session-lifetime note is appended compactly.

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?

A two-parameter, no-output-schema step in a multi-step auth flow. The session lifetime is a valuable addition, but the agent is left without guidance on error handling or what must follow on success.

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 coverage is 100% and both parameters are documented there, including the source of the reference. The description adds no meaning beyond the schema, so the baseline 3 applies.

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?

Names a specific verb and resource: verifying the SMS one-time PIN and persisting the session. That reads clearly against the sibling sixty60_login_start, though the pairing is only implicit rather than stated.

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 only implied: the sequence after sixty60_login_start comes through the reference parameter, not the description. There is no explicit when-to-use statement, no note that this must be called before any authenticated cart/order tool, and no exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server