Skip to main content
Glama

Metis ยท Librarian โ€” Search Literature

search_literature

Search your curated literature catalogue by disease, method, geography, or keyword to retrieve matching papers from your seeded database.

Instructions

Search the user's literature database.

Searches your curated/seeded literature catalogue by structured facets
(disease, method, geography, keyword). For your Zotero/manual reference
metadata use search_library; for full PDF body text use search_fulltext;
for semantic RAG over indexed PDFs use search_pdf_knowledge.

Searches the library_seeded SQLite table. Use this to find papers
by disease focus, methodology, geography, or any keyword.

Args:
    query: Search term, matched as a case-insensitive substring.
    field: Column to search -- one of "all", "disease", "method",
        "geography", or "article".
    limit: Maximum number of results to return (default 20).

Returns:
    A single TextContent holding a markdown table of matching rows from the
    library_seeded table, or an error/"no results" message if the database,
    table, or column is missing or nothing matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldNoall
limitNo
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description fully carries the burden. Discloses it searches a specific SQLite table, uses case-insensitive substring matching, returns markdown table or error message on missing data. No contradiction.

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?

Structured with purpose, sibling alternatives, details, args, returns. Every sentence adds value. Front-loaded with core purpose. No redundancy.

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?

Given no annotations and high sibling count, description sufficiently covers purpose, parameters, behavior, return format, and error handling. Output schema exists, and description complements it by describing the table format.

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?

Schema description coverage is 0%, but description explains each parameter: query as case-insensitive substring, field with allowed values (all, disease, method, geography, article), limit with default 20. Adds complete meaning beyond bare 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?

Clear verb 'search' plus specific resource 'curated/seeded literature catalogue' and explicit facets (disease, method, geography, keyword). Distinguishes from three sibling tools by naming them and their use cases.

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 sibling tools (search_library, search_fulltext, search_pdf_knowledge) for different content, and when to use this tool for structured facets. Provides clear context for agent decision.

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