Skip to main content
Glama

Server status

server_status
Read-only

Report the server version, storage locations for sessions and downloads, and whether an AnkiWeb session is stored per account. Optionally validate sessions with AnkiWeb to confirm sign-in status.

Instructions

Report the server version, where sessions and downloads are kept, and whether an AnkiWeb session is stored for each account. With validate, also ask AnkiWeb whether each session, or the one for account, is still signed 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": "server_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOmit unless the user names an AnkiWeb account. Which of the accounts signed in on this machine to act as; a name that is not one is refused with the list.
validateNoCheck the session against AnkiWeb. Starts a headless browser only when the stored cookie is missing or turned down.

Output Schema

NameRequiredDescriptionDefault
dataDirYesWhere the sessions are kept.
versionYes
accountsYesEach AnkiWeb account stored, `default` first; just `default` for most users.
readOnlyNoPresent when the server was started read-only and lists no tool that acts on AnkiWeb.
downloadsDirYesWhere downloads go when no directory is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.0.5
    • addedInput schema / properties / account
      Added value: +{
      +  "description": "Omit unless the user names an AnkiWeb account. Which of the accounts signed in on this machine to act as; a name that is not one is refused with the list.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / accounts
      Added value: +{
      +  "description": "Each AnkiWeb account stored, `default` first; just `default` for most users.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "authenticated": {
      +        "type": "boolean"
      +      },
      +      "lastValidated": {
      +        "format": "date-time",
      +        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "sessionStored": {
      +        "type": "boolean"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "sessionStored"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / authenticated
      Removed value: -{
      -  "type": "boolean"
      -}
    • addedOutput schema / properties / dataDir / description
      Added value: +"Where the sessions are kept."
    • addedOutput schema / properties / downloadsDir
      Added value: +{
      +  "description": "Where downloads go when no directory is given.",
      +  "type": "string"
      +}
    • removedOutput schema / properties / lastValidated
      Removed value: -{
      -  "format": "date-time",
      -  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
      -  "type": "string"
      -}
    • addedOutput schema / properties / readOnly
      Added value: +{
      +  "const": true,
      +  "description": "Present when the server was started read-only and lists no tool that acts on AnkiWeb.",
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / sessionStored
      Removed value: -{
      -  "type": "boolean"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "version",
      -  "dataDir",
      -  "sessionStored"
      -]New value: +[
      +  "version",
      +  "dataDir",
      +  "downloadsDir",
      +  "accounts"
      +]
  2. First observedv0.0.2

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and network profile is covered. The description adds that validation performs a live AnkiWeb sign-in check, which is useful context, but it omits what happens on failure or how long the check takes; the headless-browser detail lives only in the schema.

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, zero padding, with the core reporting behavior front-loaded and the optional `validate` mode stated second. Every clause carries information.

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?

With an output schema present, return values need no explanation, and the description covers both the informational output and the optional network check. A note on failure behavior when `validate` cannot reach AnkiWeb would make it fully self-contained.

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. The description goes further by explaining the interaction between the two parameters — `account` scopes validation to a single account while omitting it checks all sessions — which the schema documents individually but not relationally.

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?

The description opens with a specific verb and enumerates exactly what is reported: server version, session/download storage locations, and per-account AnkiWeb session presence. This clearly separates it from all deck- and session-oriented siblings without needing to name them.

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?

It explains the conditional branch for `validate` — the tool additionally queries AnkiWeb when that flag is set — which is the only meaningful usage decision here. It does not name alternatives or exclusions, but none of the listed siblings overlap with a diagnostic status report.

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