Skip to main content
Glama

HokuHost Domains

sign_in

Sign in or create an account. Call with email → user gets a 6-digit code by email; call again with email+code → signed in (API key).

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": {
      "email": "<email>"
    },
    "name": "sign_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNo6 digits from the email
totpNoonly if the answer says totp_required: the current code from the owner's authenticator app
emailYes
key_nameNooptional, e.g. Claude

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, open-world, non-destructive operation; the description adds the crucial behavior that the first call triggers a 6-digit email and the second returns an API key. It omits rate limits, code expiry, and what the intermediate response looks like, so it is strong but not exhaustive.

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 the core purpose front-loaded and the flow compressed into an arrow sequence. No filler, and every clause conveys a distinct fact.

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 two-step auth flow with four parameters and no output schema, the description covers the essential mechanics. It leaves a small gap: the schema references a 'totp_required' answer, but the description never explains that the first response can demand a TOTP step, so the agent learns that only from the schema.

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?

Schema coverage is 75%, with code, totp, and key_name already documented. The description still adds flow-level meaning the schema cannot convey: which parameters apply on which call (email alone first, email+code second), clarifying that the two calls are distinct parameter states rather than optional extras.

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 ('Sign in or create an account') and then spells out the two-call authentication flow, which no sibling tool (account, setup_card) covers. An agent can immediately tell this is the credential-acquisition tool rather than an account-inspection tool.

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 arrow notation gives explicit sequencing guidance: first call with email only, second call with email plus the code. It does not name alternatives or state when not to use it (e.g., when already holding a valid API key), so it falls short of a 5.

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