Skip to main content
Glama

get_index_stats

Retrieve vector index statistics for your active project. Verify chunk count, embedding model, and chunking configuration to confirm reindex completion.

Instructions

Show vector index statistics for the active project. Read-only, no side effects.

    Use to check how many chunks are indexed, verify a reindex completed,
    or inspect the embedding model and chunking configuration.
    Use check_knowledge_quality() instead when you want quality issues, not stats.

    Args:
        project: Target project name (optional)

    Returns:
        Total chunk count, docs path, embedding provider and model,
        chunking strategy, and per-document-type chunk distribution.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, but description declares read-only, no side effects, and lists return fields. Some missing details like permissions or error handling, but sufficient.

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?

Well-structured with paragraphs and bullet points, concise with essential information. Slightly verbose in returning details, but acceptable.

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?

In context of one optional parameter and output schema, description covers purpose, usage, and return values completely.

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

Parameters3/5

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

Schema description coverage is 0%, but description adds meaning for 'project' as optional target project name. Adequate but not extensive.

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?

Description clearly states it shows vector index statistics, is read-only, and distinguishes itself from sibling tool check_knowledge_quality.

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 (check chunk counts, verify reindex, inspect config) and when not to (use check_knowledge_quality for quality issues), providing clear alternatives.

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/dl4rce/flaiwheel'

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