aukro-mcp

Check Aukro Authentication Status

aukro_auth_status

Read-onlyIdempotent

Checks the current authentication mode and verifies whether the Aukro.cz session is actively logged in via the actualStatistics endpoint.

Instructions

Check whether the MCP server is currently running in anonymous mode, cookie session mode, or OAuth2 Bearer token mode, and verify against Aukro.cz's /users/actualStatistics endpoint whether the session is actively logged in.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: it performs a live outbound verification against Aukro.cz's /users/actualStatistics endpoint, which tells the agent the result depends on network reachability and remote session state rather than local config alone.

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?

It is a single front-loaded sentence with the verb and object first and no filler. The enumeration of the three modes is slightly verbose but each mode is meaningful information for interpreting the result.

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?

There is no output schema, so the description should explain what the check returns (e.g. the detected mode and a logged-in boolean). It states what is verified but not the shape or values of the response, leaving the agent to guess how to interpret results.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The schema's empty properties object is consistent with the description, which describes no inputs.

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 verb (check/verify) and resource (the server's auth mode plus session validity against Aukro.cz's /users/actualStatistics), and it enumerates the three possible modes. It does not, however, distinguish itself from siblings like aukro_login_interactive, aukro_logout or aukro_set_credentials, which an agent could easily confuse with an auth-related tool.

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 agent can infer this is a pre-flight/diagnostic check to run before authenticated calls, but the description never says when to call it, when not to, or to use aukro_login_interactive when it reports anonymous mode. No explicit routing to alternatives is given.

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