Skip to main content
Glama

kavita_stats

Read-only

Retrieve Kavita server statistics and reading analytics for users, libraries, genres, authors, series, devices, and file counts to analyze reading activity.

Instructions

kavita_stats covers the stats toolset (33 operations). Auth is the x-api-key header, or a JWT from KAVITA_USERNAME and KAVITA_PASSWORD. Self-hosted Kavita only. action help with target returns one action's parameters. Actions: get_avg_time_by_hour, get_day_breakdown, get_device_client_type, get_device_device_type, get_favorite_authors, get_files_added_over_time, get_genre_breakdown, get_most_active_users, get_page_spread, get_pages_per_year, get_popular_decades, get_popular_genres, get_popular_libraries, get_popular_people, get_popular_reading_list, get_popular_series, get_popular_tags, get_reading_activity, get_reading_counts, get_reading_history, get_reading_history_series, get_reading_pace, get_reads_by_month, get_server_count_manga_format, get_server_count_publication_status, get_server_file_breakdown, get_server_stats, get_tag_breakdown, get_total_reads, get_user_read, get_user_stats, get_word_spread, get_words_per_year.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "kavita_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON body for the Kavita operation. Secrets are redacted in output.
queryNoOpenAPI query parameters.
actionYesKavita operation to call, or help.
paramsNoOpenAPI path parameters, such as seriesId.
targetNoWith action help, the action whose parameters to describe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered, and the description adds genuinely new context: authentication via x-api-key header or JWT derived from KAVITA_USERNAME/KAVITA_PASSWORD, and the self-hosted-only deployment constraint. It does not describe result shape or any rate/timeout behavior, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentences (scope, auth, deployment, help mechanism) are front-loaded and earn their place. The 33-item action list is a long inline enumeration that duplicates the enum already in the schema, making the description bulky without adding discriminating 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?

For a 33-operation multiplexed tool with no output schema, the definition covers scope, auth, deployment constraint, and the discovery path (action=help + target) that an agent needs to call any individual action correctly. It leaves unclear which parameters each action requires without the help round-trip and says nothing about return values, which keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so body, query, params, action and target are all documented structurally. The description only adds meaning for one of them — that target is used together with action=help to fetch parameter details — and otherwise restates the action enum already present in the schema, so baseline 3 is appropriate.

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 the resource domain (Kavita reading/server statistics) and enumerates all 33 concrete operations, so an agent can see exactly which facts this tool retrieves rather than guessing. It is distinguishable from siblings like kavita_library or kavita_series by the enumeration, though it never states the purpose in a single explicit verb+resource phrase ('retrieves reading and server statistics').

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?

It gives useful operational routing: 'action help with target returns one action's parameters' tells the agent how to discover per-action schemas instead of guessing. However, it offers no guidance on when to pick this tool over siblings (e.g. kavita_server also exposes server-level data) and no exclusions or prerequisite conditions beyond 'Self-hosted Kavita only'.

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