Skip to main content
Glama

get_pdf_index_stats

Check the indexing status and coverage of your PDF knowledge bases. View document and chunk counts, last build time, and un-indexed PDFs to ensure your RAG corpus is complete.

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

TableJSON Schema
NameRequiredDescriptionDefault
databaseNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It describes that the tool returns per-database counts, last-built time, domain breakdown, and un-indexed PDFs, making its behavior clear. It is read-only, and no destructive effects are 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 concise and well-structured: a one-sentence summary, a usage context paragraph, a parameter section, and a returns section. Every sentence earns its place.

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 the tool's complexity (reporting on multiple databases with various metrics) and the existence of an output schema, the description adequately covers what the agent can expect. It might benefit from mentioning pagination or limits, but is otherwise complete.

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 coverage is 0%, but the description fully explains the sole parameter 'database': its meaning (slug for a single database), an example, and the default behavior (reports on all databases). This adds significant value 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?

The description states 'Report indexing status and coverage for your PDF knowledge bases', which is a clear verb+resource. It distinguishes from siblings like index_pdf_library and search_pdf_knowledge by specifically focusing on indexing status and coverage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says 'Use this to check how complete your RAG corpus is before relying on grounded answers', providing a clear use case. It also mentions complementary tools (index_pdf_library and search_pdf_knowledge), though does not give explicit when-not scenarios.

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