Skip to main content
Glama

search_library

Find papers in your local library by searching title, authors, abstract, and tags. Results show newest papers first.

Instructions

Search the local literature library for matching papers.

Searches your saved reference METADATA (title/authors/abstract/tags of papers
in your Zotero-synced + manual library). For meaning-based search inside PDF
body text use search_pdf_knowledge; for exact keyword search of PDF text use
search_fulltext; for an online/external literature lookup use search_literature.

Runs a substring search across the user's indexed references (Zotero-synced
plus manually added) so you can find what they already have before going to
the internet. Matches the query against title, authors, abstract, and tags,
returning the newest papers first. For richer literature workflows see
ask_library, search_literature, and export_citations.

Args:
    query: Search terms matched as a substring against title, authors,
        abstract, and tags.
    limit: Maximum number of papers to return, ordered newest year first
        (default 10).

Returns:
    A formatted text list of matching papers (title, authors, year, journal,
    DOI, abstract snippet), or a "no papers found" message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses substring matching, fields searched, ordering (newest first), and return format. No annotations, so description carries full burden; it is adequate but could mention case sensitivity or pagination.

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?

Well-organized with clear sections: main purpose, usage alternatives, parameter details, and return format. No wasted sentences.

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?

Covers all aspects: what it does, when to use, input parameters, output format. Simple tool with two parameters, fully described.

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 0%, but description explains both 'query' (substring match against fields) and 'limit' (max results, default 10), adding meaning beyond 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?

Description clearly states it searches local literature metadata (title/authors/abstract/tags) and distinguishes from sibling tools like search_pdf_knowledge, search_fulltext, search_literature.

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 tells when to use this tool vs. alternatives: meaning-based PDF search, exact PDF keyword search, or external literature lookup. Also clarifies it searches user's own references.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server