Skip to main content
Glama

dev_tools_totp

[$x402 pago por llamada] Genera un código TOTP según RFC 6238.

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": {
      "secret": "<secret>"
    },
    "name": "dev_tools_totp"
  }
}

Input Schema

NameRequiredDescriptionDefault
algoNoAlgoritmo de hash. Default: `sha1`.
digitsNoCantidad de dígitos del código (6-8). Default: 6.
periodNoPeríodo en segundos (15-300). Default: 30.
secretYesSecreto Base32 RFC4648 (formato Google Authenticator).
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description still contributes real behavioral context: the tool is paid per call via x402, and if payment is omitted the call returns 402 with requirements. That is useful auth/cost disclosure. It says nothing about how the secret is handled, whether codes are cached, or the time-window semantics of the emitted code.

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 compact clauses with no filler; the pay-per-call marker is front-loaded and the RFC reference follows immediately. Slightly terse for a security-sensitive tool, but nothing is wasted.

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 single-output generator with fully documented parameters and no output schema, the essentials are covered, but the description never explains what the caller receives (a code string plus expiry/window) or how to interpret it. Adequate but with a clear gap around return semantics for a time-based token.

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 description coverage is 100%, so algo, digits, period, secret and x_payment are all documented in the schema, including defaults and ranges. The description adds no parameter meaning beyond the schema, so the baseline of 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?

States a concrete verb (Genera) and resource (código TOTP) with the governing standard (RFC 6238), which is enough to distinguish it from siblings like dev_tools_hmac or dev_tools_password_generate. It does not, however, explicitly contrast itself with those neighbors.

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 statement of when to choose this over dev_tools_hmac or dev_tools_password_generate, nor any prerequisite beyond the pay-per-call tag. The agent must infer usage entirely from the tool name and RFC reference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources