Skip to main content
Glama

Search my Knacco library

knacco_search_library
Read-only

Find owned products using case-insensitive substring matching against original and localised titles, subtitles, product types and tags. Returns the same paginated item summaries as knacco_list_library, newest entitlement first; empty items means no matches on that page. Use knacco_list_library to browse without a query. Requires library:read; does not search unowned store products.

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

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page number, default 1. Returns up to 50 products; use nextPage from the response to continue.
queryYesPlain text to match as a substring, 1–200 characters after trimming. No Boolean operators, wildcards or fuzzy matching.
localeNoLanguage for product text: en or he. Defaults to the connected account language; untranslated fields fall back to their original text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, closed-world, non-destructive), and the description adds real value on top: required scope library:read, newest-entitlement-first ordering, and the meaning of an empty items array on a page. It does not spell out pagination mechanics, but the schema already documents nextPage, so the gap is small.

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?

Three dense sentences, front-loaded with the match semantics, then return behavior, then the sibling pointer and constraints. Nearly every clause carries information, though the paragraph is packed enough that the permission note feels appended rather than structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still tells the agent what comes back (paginated item summaries identical to knacco_list_library, newest entitlement first) and how to read an empty result. Combined with auth scope and scope exclusions, nothing needed to invoke it correctly is missing.

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 rises above it by explaining which fields the query matches against (original and localized titles, subtitles, types, tags), which the schema does not say. It deliberately does not restate the substring/locale rules already in the schema.

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 first sentence names a specific verb (find), resource (owned products), and matching rule (case-insensitive substring over titles, subtitles, product types, tags). The contrast with knacco_list_library ('browse without a query') makes the boundary between the two tools unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool (a query exists) and names the alternative for the no-query case (knacco_list_library). It also states a scope exclusion — 'does not search unowned store products' — which prevents a plausible misuse.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources