Skip to main content
Glama

Semerenko Group Public Site MCP

Get indexing and crawler status

sem.get_indexing_status
Read-only

Return public IndexNow, sitemap, llms, robots, and agent discovery state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sem.get_indexing_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety and locality profile is covered. The description adds one useful qualifier — the state is "public" — implying these are externally visible discovery artifacts rather than internal crawler bookkeeping, but it says nothing about freshness, caching, or whether a missing entry means "not configured" or "not yet crawled."

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?

A single front-loaded sentence with no filler; every listed noun maps to a distinct piece of returned state. Nothing could be removed without losing information.

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 no-parameter, read-only status tool with annotations covering the safety profile, the description gives an unusually explicit inventory of what state is reported. The only residual gap is that with no output schema, it does not hint at the shape of each entry (e.g. whether sitemap state is a URL, a count, or a boolean).

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no words on inputs.

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?

Names a specific verb ("Return") and enumerates the concrete artifacts whose state is returned: IndexNow, sitemap, llms, robots, and agent discovery. An agent can tell this reports discovery/indexing artifacts rather than site content or infra, though it does not explicitly distinguish itself from neighbors like sem.get_ai_infra_status or sem.get_site_inventory.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives, no prerequisites, and no exclusions. The agent must infer the trigger condition ("I want to know if the site is discoverable/indexable") entirely from the purpose sentence.

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