Skip to main content
Glama

kavita_search

Read-only

Search a self-hosted Kavita library to find series, list chapters by series, and map chapters or manga files to their series.

Instructions

kavita_search covers the search toolset (4 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_chapters_by_series, get_search, get_series_for_chapter, get_series_for_mangafile.

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_search"
  }
}

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile needs no restating. The description adds meaningful context the annotations do not: the auth mechanism (x-api-key header or JWT from KAVITA_USERNAME/KAVITA_PASSWORD), the self-hosted-only constraint, and that secrets are redacted in output. It omits return shape and pagination behavior for the individual actions.

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?

Front-loaded with scope, then auth, then environment constraint, then the help mechanism, then the action list—logical order with no filler. The auth sentence is dense (two credential paths) but each clause carries operational information an agent needs before calling.

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 5-parameter nested dispatcher with no output schema, the description covers scope, auth, environment limitation and a self-describing help action, which is enough for correct invocation. What is missing is per-action semantics and any hint about what the actions return; the help action partially compensates by letting the agent retrieve per-action parameters on demand.

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 the schema already documents action, params, query, body and the help/target coupling; the description largely restates the action enum. The one added nuance is the help+target pattern for introspecting per-action parameters, which is useful but also already stated in the target field description. Baseline 3 applies.

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 frames this as a 4-operation search dispatcher and enumerates every action (get_chapters_by_series, get_search, get_series_for_chapter, get_series_for_mangafile), which distinguishes it from the resource-specific siblings like kavita_series and kavita_chapter. It does not explain what each action actually does, so the agent still cannot tell get_search from get_series_for_chapter without calling help or opening the schema.

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 by the action list and by the 'action help with target' discovery path, which is a genuine affordance for figuring out parameters. However, there is no explicit when-to-use-this-vs-siblings statement, e.g. whether to fetch a series via kavita_series instead of get_series_for_chapter, and no preconditions beyond auth.

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