Skip to main content
Glama

Hive login status

hive_auth_status
Read-only

Check if this server is logged in to Hive: shows the masked account email, remembered device status, token expiry and any login error, without exposing passwords or secrets.

Instructions

Show whether this server is logged in to Hive: the account (with the email address masked), whether this server is a remembered device (so it can log in again without an SMS code), when the current token expires and any login error. Never shows passwords, tokens or device secrets.

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": "hive_auth_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the email is masked, the remembered-device flag explains SMS-free re-login, token expiry is exposed, and it explicitly promises that passwords, tokens, and device secrets are never returned. That last sentence is a useful disclosure an agent could not derive from structured fields.

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?

A single sentence led by the core question ("is this server logged in") followed by the returned data, with the privacy guarantee front-loaded at the end. No filler or restatement of the name and title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no parameters, so the description carries the full burden of describing the response – and it does so by enumerating each returned element, including the error case. For a zero-argument status tool, nothing an agent needs in order to call it or interpret the result is missing.

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?

This tool takes zero parameters, which is the baseline-4 case. The description correctly describes a no-argument call and spends its words on the return payload rather than inventing parameter meaning.

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 ("Show whether this server is logged in to Hive") and then enumerates the exact fields returned: account with masked email, remembered-device flag, token expiry, and login error. That is far more concrete than the title alone. It does not explicitly name any sibling as an alternative, but the auth-status scope is unambiguous next to the heating/device sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the field list – an agent can infer this is the tool to call when it needs to confirm authentication state before invoking a heating/device tool. There is no explicit when-to-use statement, no mention of when not to use it, and no routing to an alternative.

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