sixty60-mcp

Start Sixty60 login

sixty60_login_start

Sends a one-time SMS PIN to a Sixty60 account's mobile number and returns a reference to pass to the login verify step with the code the user receives.

Instructions

Send a one-time PIN by SMS to the Sixty60 account's mobile number. Returns a reference to pass to sixty60_login_verify with the code the user receives.

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

Input Schema

Name	Required	Description	Default
`mobile`	No	Mobile number in international format, e.g. +27821234567. Defaults to the last one used.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key behavioral trait: an SMS is sent to the user as an external side effect, and a reference is returned for the next step. It omits secondary behavior such as PIN expiry, rate limits, or whether a repeat call invalidates a prior PIN, which keeps it from a 5.

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 sentences, front-loaded with the action and side effect, followed by the return contract and next step. No redundant or filler wording.

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 single-optional-parameter tool with no output schema, the description covers the action, the side effect, and what is returned and how to use it. Only edge-case behavior (expiry, resend semantics, failure modes) is left unaddressed.

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 the schema already documents the mobile format, pattern, and default-to-last-used behavior. The description only restates that the number belongs to the Sixty60 account, adding little 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.

Purpose5/5

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

States a specific verb and resource ('Send a one-time PIN by SMS to the Sixty60 account's mobile number') and explicitly names the sibling it feeds into, sixty60_login_verify, so an agent can distinguish the two login steps without opening either schema.

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?

The description makes the usage flow clear: call this first, then pass the returned reference to sixty60_login_verify along with the code the user receives. It does not state when not to use it (e.g. if a PIN is already outstanding), but the sequencing guidance is explicit.

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

Deploy Server