Skip to main content
Glama
Sign In
sixty60-mcp

sixty60-mcp

by matogen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Log out of Sixty60

sixty60_logout

Clears the saved Checkers Sixty60 session so the user is signed out. Use it to remove stored login credentials and reset authentication state before signing in again.

Instructions

Delete the saved Sixty60 session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the full burden, and it does at least disclose the effect: saved session state is deleted. It omits important behavior for a mutation tool — whether the server-side session is revoked or only the local credential is discarded, whether the call is idempotent, and what happens if no session exists.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently sized, though the brevity is achieved by omission rather than by tight editing of richer content.

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, no-output-schema tool the description is close to sufficient, but with no annotations at all a caller must infer permissions, error behavior, and post-conditions entirely from the name. One added clause on session invalidation or failure behavior would make it complete.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter meaning is lost or misrepresented.

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 gives a specific verb and resource: "Delete the saved Sixty60 session." That is unambiguous about what is removed and clearly distinguishes it from the login siblings (login_start, login_verify) whose names imply the opposite direction. It stops short of 5 because it never contrasts itself with any sibling by name.

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 guidance on when to call this versus alternatives, no prerequisite (an existing session must exist), and no mention of what a caller should do afterwards. The usage is only inferable from the tool name and the word 'logout' in the title.

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