Skip to main content
Glama

auth_status

Reports local configuration and login status without exposing passwords, keys, or cookies; enable check_login to verify teaching-site and portal access and auto re-login when sessions expire.

Instructions

本机配置与登录状态(不含密码、密钥、Cookie)。check_login=true 时实际验证教学网和门户,失效会自动重新登录。

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
check_loginNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it discloses two non-obvious traits: the response excludes secrets (passwords, keys, cookies), and check_login=true performs real verification with automatic re-login on expiry — a side effect an agent would otherwise not anticipate. It still omits the cost/latency of that verification and any failure modes.

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 sentences, no filler, with the data-scope caveat and the conditional verification behavior each stated once and front-loaded. Nothing repeats 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?

A low-complexity, single-parameter tool with an output schema, so return values need not be explained. The remaining gap is the absent relationship to auth_setup and the unstated cost of check_login=true, minor for a status tool but not negligible.

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 description coverage is 0%, so the description must explain the single parameter, and it does: check_login=true means actual verification against the teaching site and portal, with auto re-login on expiry. Only the default value (false) is left to the schema, and the description never states what is returned in each branch, but the meaning of the flag is well conveyed.

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 specifies the resource precisely: local configuration plus login status, with an explicit data boundary ("不含密码、密钥、Cookie"). It reads clearly as a status-inspection tool distinct from a sibling like auth_setup, though it never names or contrasts with that sibling directly.

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: the check_login=true branch signals when a deeper verification is appropriate. There is no explicit guidance on when to call auth_status versus auth_setup, nor on when to leave check_login at its default (false) to avoid triggering network round-trips.

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