Skip to main content
Glama

List my Knacco library

knacco_list_library
Read-only

Browse the authenticated account’s owned products, newest entitlement first. Returns items with slug, title, subtitle, type, contentLanguage, coverImageUrl and agentAccess, plus page and optional nextPage. An empty items array means no products on that page. Use knacco_search_library to filter by text, then knacco_get_product_guide for instructions and file identifiers. Requires library:read; does not search the store catalog.

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

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page number, default 1. Returns up to 50 products; use nextPage from the response to continue.
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.5/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/destructive=false, but the description adds real context beyond them: the required library:read scope, entitlement ordering, the meaning of an empty items array, and the nextPage continuation. It stops short of saying whether revoked or unpublished products still appear, which is the one behavioral question an agent might still have.

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?

Four sentences, front-loaded with purpose, then return shape, then edge case, then routing and precondition. No sentence is redundant with another and none repeats the title.

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?

Although there is no output schema, the description enumerates the returned fields, the envelope (page, optional nextPage) and the empty-page case, so return values are covered. Combined with the auth scope and sibling routing, nothing needed to call it correctly is missing.

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 both page and locale are already documented in the schema, including the enum values and the 50-item page size. The description only adds the ordering guarantee and the page/nextPage relationship in the return shape, so the baseline of 3 holds.

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?

States a specific verb and resource ('browse the authenticated account's owned products'), the ordering ('newest entitlement first'), and an explicit exclusion ('does not search the store catalog'). An agent can distinguish it from knacco_search_library purely from this sentence.

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?

Routes the agent explicitly: use knacco_search_library for text filtering and knacco_get_product_guide for instructions and file identifiers, implying this tool is the unfiltered browse. Prerequisites are named ('Requires library:read') and out-of-scope behavior is stated.

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