Skip to main content
Glama

check_sitemap

Check sitemap count, lastmod values, and noindex pages to spot indexing issues and prioritize fixes.

Instructions

检查 sitemap 的数量、lastmod 与 noindex 页面。

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": {
      "url": "<url>"
    },
    "name": "check_sitemap"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes完整的 http:// 或 https:// URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it says nothing about whether the URL is fetched live over the network, whether the call is read-only, how failures (unreachable sitemap, malformed XML) are surfaced, or how sitemap indexes are traversed. For a network-dependent inspection tool with zero annotation coverage, this is a substantial gap.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the terseness leaves no room for the scoping detail the tool would benefit from.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one fully documented parameter and no output schema, the description is minimally sufficient to invoke the tool correctly. However, for a tool that fetches remote content with no annotations, the absence of any behavioral or result-format context leaves clear gaps.

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?

There is a single parameter and the schema already documents it at 100% coverage ("完整的 http:// 或 https:// URL"), so the schema does the heavy lifting. The description adds no further constraint, such as whether the URL must point directly at a sitemap file versus a sitemap index or site root; baseline 3 applies.

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?

"检查 sitemap 的数量、lastmod 与 noindex 页面" gives a specific verb (check) and resource (sitemap) plus the exact facets inspected (count, lastmod, noindex pages), so an agent knows what it returns conceptually. It does not explicitly distinguish itself from siblings like check_robots or run_audit, which is the only thing keeping it from a 5.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives such as run_audit, which could plausibly cover sitemap checks too. Usage is only inferable from the tool name.

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

Deploy Server

Other Tools