Skip to main content
Glama

Metis · Librarian — Search Pdf Knowledge

search_pdf_knowledge

Retrieve relevant PDF chunks from your knowledge base using semantic search. Query with natural language to find cited answers from indexed documents.

Instructions

Semantic search across one or more knowledge database layers.

Meaning-based (vector) search over your knowledge-base PDF chunks — the RAG
retrieval tool behind grounded, cited answers. For exact keyword matches use
search_fulltext; for reference metadata use search_library; for your own
notes/memory (not documents) use semantic_search.

Searches indexed PDF chunks using 768-dim nomic-embed vector similarity.
You can search a single layer or combine layers (e.g. PH background + HAT specialist).

Args:
    query: Natural language question or keyword phrase to embed and match.
    databases: List of database slugs to search; pass None (the default) to
        search all indexed databases. Examples: ['ph-background'],
        ['hat-specialist', 'epi-methods'].
    top_k: Number of results to return (default 8).

Returns:
    A single TextContent listing the top-ranked PDF chunks (title, similarity
    score, layer, domain, page, source file, and an excerpt), or a message if
    nothing is indexed yet or no chunks match the requested databases.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
top_kNo
databasesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden. It explains the vector search method (768-dim nomic-embed), result structure (title, score, layer, etc.), and behavior for no matches. It could mention that it only searches indexed PDF chunks, but the mention of 'nothing is indexed yet' implies this. Overall transparent.

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 concise yet thorough, with clear sections: purpose, sibling comparison, technical detail, args, and returns. It uses about 10 sentences with no unnecessary words, front-loading the most critical information.

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 the tool's moderate complexity (3 parameters, no nested objects) and the output schema existing (described as TextContent with detailed result format), the description is complete. It covers input semantics, behavioral constraints, return values, and usage context. No gaps evident.

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 description adds significant meaning beyond the input schema's type/default info. It provides natural language explanations for each parameter (query, databases, top_k), includes examples for databases, and clarifies the role of query as 'natural language question or keyword phrase.' This compensates for the 0% schema description coverage.

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's purpose: 'Semantic search across one or more knowledge database layers.' It identifies the specific verb (search) and resource (PDF knowledge), and distinguishes from siblings by specifying when to use alternatives like search_fulltext, search_library, and semantic_search.

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?

The description provides explicit guidance on when to use this tool and when to use alternatives: 'For exact keyword matches use search_fulltext; for reference metadata use search_library; for your own notes/memory (not documents) use semantic_search.' This helps the agent choose correctly.

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