Skip to main content
Glama

(Re)index the agent's website

start_site_indexing

Start or refresh the index of the agent's own website (sitemap + link crawl, JS pages read in a headless browser, shop catalogue detection). Rate-limited to 12 runs/hour per user. force=true re-reads even a fresh index. 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": "start_site_indexing"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a solid job: it discloses the crawl mechanisms (sitemap + link crawl, headless browser for JS pages, catalogue detection), a hard rate limit of 12 runs/hour per user, and that the operation is free. It omits whether the run is asynchronous, how long it takes, or what happens on failure, which for a potentially long crawl is a meaningful gap.

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?

Two dense sentences with zero filler: purpose first, then mechanics, constraint, parameter semantics, and cost. Each clause carries information an agent would otherwise have to guess.

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?

For a two-parameter, no-output-schema, no-annotation tool, this covers most of what is needed: cost, quota, crawl behavior, and the non-obvious flag. The remaining gap is operating behavior — synchronous vs job-based completion and how to follow progress — which matters given a sibling exists for index status.

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%, so the description must compensate. It fully explains the meaning of force (re-reads even a fresh index), but agent_id is never mentioned beyond the phrase "the agent's own website" — the agent must infer that it is the target agent identifier and is required. Half the parameters are effectively covered.

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 states a specific verb+resource ("Start or refresh the index of the agent's own website") and scopes it to the agent's own site, which distinguishes it from site-wide scanners and index-status siblings. It stops short of naming an alternative tool, but the operation is unambiguous.

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?

"Start or refresh" implies the use case (build the index, or rebuild it later), and "force=true re-reads even a fresh index" gives a concrete trigger for the forced variant. However, no when-not guidance or alternative is named (e.g. checking get_site_index_status before re-running), so routing is left 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