Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Enable Totp

enableTotp
Destructive

Enable time-based one-time password (TOTP) by providing the setup secret and a current app code; future sign-ins will require a code from the authenticator app.

Instructions

Takes the key from startTotpSetup and a current code from the app. From then on every sign-in asks for a code from the 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": "enableTotp"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestBodyNoThe JSON request body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already disclose readOnlyHint=false, destructiveHint=true, and openWorldHint=true. The description adds real context beyond them: the change is persistent and affects the authentication path for all future sign-ins, which explains the destructive framing. It does not mention recovery-code handling or what happens on an invalid code, leaving a modest gap.

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 short sentences with no filler; the prerequisite is stated first and the lasting effect second, matching the order an agent needs to reason about the call. Nothing is repeated from the name or schema.

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-parameter tool with a fully described schema, no output schema, and annotations carrying the safety profile, the description covers the prerequisite, the inputs, and the persistent effect. It could be slightly more complete by noting whether recovery codes are surfaced or what a rejected code looks like.

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%, so the nested requestBody fields and their patterns are already documented, making 3 the baseline. The description does add meaning the schema cannot -- that 'secret' is the key from startTotpSetup and 'code' is a current, live code from the authenticator app -- but it does not address the edge cases the enforced patterns imply.

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 conveys a specific action and effect: it consumes the key produced by startTotpSetup plus a live app code, and thereafter every sign-in requires a code. The verb 'enable' is only implicit in the name, but the stated outcome makes the operation unmistakable and distinguishes it from the sibling startTotpSetup (which only produces the key).

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?

It explicitly establishes the prerequisite sequencing -- the secret must come from a prior startTotpSetup call -- which is exactly the routing information an agent needs before invoking it. There is no explicit when-not guidance or mention of disableTotp as the inverse, so it stops short of full alternative coverage.

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