Skip to main content
Glama

auth_status

Idempotent

View authenticated-crawling identity-pool status by source: identity counts, five-state status distribution, leased counts, pool totals, and login stations; add a source for detail rows. Read-only.

Instructions

Authenticated-crawling identity-pool overview.

Per source: identity count, the five-state status distribution (login_required / active / cooldown / banned / retired) and the currently-leased count; plus pool-level totals and the in-flight login-station count (stations.active — launching / waiting for operator; login-station-console). With source: also the detail rows for that source's identities (account, status, automation, last login/success, zero-run streak, lease view) — an unknown source returns zero totals and empty rows, not an error. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
sourceNorestrict to one source (adds the detail rows).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior1/5

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

The description ends with an explicit claim of "Read-only", while the supplied annotations declare readOnlyHint=false. That is a direct conflict between natural-language behavior and structured metadata, so an agent cannot tell whether this is a safe inspection call or one with side effects. The rest of the description is informative (unknown sources return zero totals rather than an error), but the read-only contradiction dominates the behavioral assessment.

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?

The description is front-loaded with the one-line purpose, then progressively details per-source fields, pool-level totals, and the source-scoped detail rows. It is dense with parenthetical asides ("launching / waiting for operator; login-station-console") but nearly every clause carries concrete information; a small amount of the field enumeration duplicates what the output schema already provides.

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?

Return value shape is largely covered by the existing output schema and the description's field enumeration, and the unknown-source behavior is spelled out, so the informational side is solid. Completeness is undercut by the "Read-only" claim that conflicts with readOnlyHint=false, leaving the tool's side-effect profile unresolved for a 1-parameter aggregation tool.

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 100%, so the baseline is 3 for what the ``source`` parameter means and its default of null. The description adds value beyond the schema by disclosing that an unknown source yields zero totals and empty rows rather than an error, which is real behavioral meaning not captured in the property definition.

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 names a specific resource and framing ("Authenticated-crawling identity-pool overview") and enumerates exactly what it aggregates: per-source identity counts, the five-state distribution, leased counts, pool totals, and the login-station count. An agent can tell this is a reporting/aggregation tool rather than an action tool, though it never explicitly contrasts itself with siblings like auth_events or crawl_status.

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 implied rather than stated: the tool is for inspecting pool status, and the optional ``source`` argument is described as restricting to one source and adding detail rows. There is no explicit "use this when / use X instead" guidance distinguishing it from auth_events or crawl_status, and no stated prerequisites such as needing a source to exist first.

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