Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis · Librarian — Get Pdf Index Stats

get_pdf_index_stats

Check PDF knowledge base indexing status and coverage before relying on retrieval answers. Reports document and chunk counts, last build time, domain breakdown, and un-indexed PDFs.

Instructions

Report indexing status and coverage for your PDF knowledge bases.

Use this to check how complete your RAG (retrieval) corpus is before
relying on grounded answers: it shows, per knowledge database, the document
and chunk counts, when it was last built, a domain breakdown, and which PDFs
are still un-indexed. A quick "is my library ready to answer questions?"
health check. Pairs with index_pdf_library (to index) and
search_pdf_knowledge (to query).

Args:
    database: Slug of a single knowledge database to report on (e.g.
        "ph-background"). Empty string (the default) reports on every
        database.

Returns:
    A formatted status report covering each database's counts, last-built
    time, domain breakdown, and any un-indexed PDFs.

Input Schema

NameRequiredDescriptionDefault
databaseNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It describes the tool as a reporting function with no side effects, which is clear. However, it does not explicitly state that it is read-only or non-destructive, though implied.

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 efficiently structured: a concise purpose sentence, a usage paragraph, and then explicit Args and Returns sections. No unnecessary words.

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?

The description covers the tool's purpose, input, output contents, and sibling relationships. With output schema present, the return description is sufficient. Complete for a single-parameter reporting 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 single parameter 'database' has no schema description (0% coverage), but the description explains its default behavior (empty string reports all databases), provides an example slug, and clarifies its optional nature. This fully compensates for the lack of schema description.

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 'Report indexing status and coverage for your PDF knowledge bases' and specifies the data shown (counts, last built, domain breakdown, un-indexed PDFs). It explicitly distinguishes from sibling tools index_pdf_library and search_pdf_knowledge.

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 explains when to use: 'check how complete your RAG corpus is before relying on grounded answers' and pairs with related tools for indexing and querying. This provides clear context and alternatives.

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

Deploy Server

Other Tools