Skip to main content
Glama

get_pdf_index_stats

Assess indexing completeness of your PDF library. Displays document and chunk counts, last build time, domain breakdown, and un-indexed PDFs per knowledge database to confirm RAG readiness.

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
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, idempotency, or safety. Since this is a read-only report tool, the description should explicitly state it has no side effects, but it does not.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose statement, usage context, parameter documentation, and return value explanation. It is slightly verbose but remains focused and informative.

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 presence of an output schema, the description adequately explains the return value as a 'formatted status report' covering specific details. No additional information is necessary for an agent to understand what the tool returns.

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

Parameters4/5

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

Schema description coverage is 0%, but the description provides a detailed explanation of the 'database' parameter, including its meaning, example value, and default behavior. This compensates for the lack of schema descriptions.

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 verb 'Report' and the resource 'indexing status and coverage for your PDF knowledge bases'. It distinguishes from sibling tools by naming index_pdf_library and search_pdf_knowledge as related but distinct tools, providing clear differentiation.

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?

The description explicitly states when to use: 'to check how complete your RAG corpus is before relying on grounded answers' and pairs with related tools for indexing and querying. It lacks explicit when-not-to-use guidance, but the context is clear enough.

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_PH'

If you have feedback or need assistance with the MCP directory API, please join our Discord server