Skip to main content
Glama

Site index status

get_site_index_status

Status of the agent's website index: pages/languages/products counts, crawl progress (finding / reading / understanding / catalogue), failures with reasons, detected shop platform, subdomains. The index powers the live widget and AI-agent access to the site. Read-only, free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "get_site_index_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden and does add real value by declaring 'Read-only, free', which tells the agent there is no mutation risk or cost. However, it omits important behavior for a status tool: what happens when the index has never been started, whether crawl progress is live or a snapshot, and error semantics for an invalid agent_id.

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?

Three compact sentences: the first front-loads the return contents as a dense enumeration, followed by a purpose sentence and a cost/safety sentence. Every sentence carries content, though the parenthetical crawl-stage list is slightly dense to parse.

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?

The tool has no output schema, so the description must describe return values, and it does so well by enumerating the payload sections including failure reasons and detected platform. What is missing is edge-state behavior (index not yet started, partial crawl) and any hint about polling cadence.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description must compensate for agent_id, and it does not mention the parameter at all. The name is largely self-explanatory, but no meaning (format, accepted values, whether it can reference another agent) is added beyond the schema type.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and enumerates its contents: page/language/product counts, crawl stage progress, failures with reasons, detected shop platform, and subdomains. This clearly distinguishes it from a sibling like list_site_index_pages, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The sentence 'The index powers the live widget and AI-agent access to the site' implies why an agent would check status, but there is no explicit when-to-use or when-not-to-use guidance. It never routes the agent to start_site_indexing, add_site_pages, or list_site_index_pages for related needs, leaving selection to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources