Skip to main content
Glama

get_rag_status

Read-onlyIdempotent

Check if the RAG index is up to date for a specific source or all sources. Use to debug stale or incomplete search results.

Instructions

Report state of the RAG index for one source or all sources.

    Use this to check if the index is up to date before deciding whether to
    call `update_source_index`. Also useful for debugging when search results
    seem stale or incomplete.

    Args:
        source: Specific source name to inspect. If None, returns the
            status of every configured source.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoSource name to inspect (see `list_sources`). Omit to report the status of every configured source.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Description aligns with annotations (readOnlyHint=true, idempotentHint=true) by indicating a non-modifying status check. Adds context that it's a read operation, but annotations already cover safety profile. No contradictions.

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?

Very concise: one sentence for purpose, then usage scenarios. No fluff, front-loaded with key action, and well-structured.

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 simplicity (1 param, no required, output schema exists), the description covers purpose, when to use, and parameter behavior. Complete for an agent to invoke correctly.

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 already covers 100% of parameters with a clear description for 'source'. The tool description reiterates the same info (source name, omit for all), adding no new semantics 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?

Clearly states the tool reports the state of the RAG index for one or all sources. Uses specific verb 'report state' and identifies the resource. Distinguishes from sibling by mentioning checking before update_source_index.

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: before deciding to call update_source_index and for debugging stale search results. Implicitly suggests alternative tool (update_source_index). Provides clear context for usage.

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/lorenzo-cambiaghi/LynxMCP'

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