Skip to main content
Glama

search

Read-onlyIdempotent

Find books in your Kavita library by matching words in their titles, not summaries. Returns the same book rows as list_library, with a configurable result limit.

Instructions

Find books whose title matches, with the same rows as list_library.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords from a title (summaries are not searched)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuine value beyond that: it discloses the matching scope (title only, not summaries) and, importantly, that results carry the same row shape as list_library — useful because no output schema exists. It does not mention the result cap or ordering.

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?

A single front-loaded sentence with no wasted wording; the matching scope comes first and the row-shape note second. It is efficient, though the brevity leaves the limit behavior unaddressed rather than deliberately scoped.

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?

For a simple two-parameter read tool with strong annotations, the description covers purpose and return shape adequately. The remaining gap is the undocumented limit parameter and result cap — an agent cannot tell from the definition how many books come back or whether to raise the limit for broad queries.

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

Parameters2/5

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

Schema coverage is only 50%: query is documented in the schema, but limit (default 10, max 50) has no description anywhere. The description's "title matches" merely restates the schema's query description and says nothing about limit, pagination, or how many rows come back by default, so it fails to compensate for the coverage gap.

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?

"Find books whose title matches" gives a specific verb (find), a specific resource (books), and a precise scope (title only, not full text). It also distinguishes itself from list_library by naming it as the unfiltered counterpart via the shared row shape. It stops short of a full sibling contrast, but the agent can tell what this does at a glance.

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 rather than stated: the agent must infer that this is the tool to reach for when it has title words instead of wanting a full listing. There is no explicit "use this when / not when" guidance and no mention of what to do when the title is unknown or partial matching fails.

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