Skip to main content
Glama

Metis ยท Librarian โ€” Search Library

search_library

Search your local literature library to find papers matching your query in title, authors, abstract, or tags. Returns 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
limitNo
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that it runs a substring search across indexed references, matches against title/authors/abstract/tags, returns newest first, and returns a formatted list or no-papers message. This is good behavioral context, though it doesn't explicitly state it is read-only or mention any side effects.

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?

The description is well-structured: a concise first sentence, a paragraph explaining scope and alternatives, another on behavior, then clearly labeled Args and Returns sections. Every sentence adds value without redundancy.

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?

Given no annotations, the description covers purpose, usage guidelines, parameters, and return format. It mentions output schema implicitly by describing the return. Minor details like case sensitivity or pagination are missing, but overall it is quite complete for a search tool.

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

Parameters5/5

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

The input schema has 0% description coverage, but the description compensates fully. It explains 'query' as substring search against title/authors/abstract/tags and 'limit' as max number of papers, ordered newest first, with a default of 10. This adds significant meaning beyond the schema's type and required constraints.

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 description clearly states the tool searches the local literature library for matching papers, specifying the resource (local literature library) and the action (search). It distinguishes from siblings by mentioning alternatives for PDF body text search and online lookup, which helps the agent differentiate.

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 provides when to use: searches saved reference metadata before going to the internet, and for different types of searches (PDF body, exact keyword, online) it directs to specific sibling tools. This provides clear context and exclusions.

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