Skip to main content
Glama

indexnow_validate_key

Validates that an IndexNow key file is accessible for a host and contains the correct key, helping confirm IndexNow setup before submitting URLs.

Instructions

Validate that an IndexNow key file is accessible and contains the correct key.

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": {
      "host": "<host>"
    },
    "name": "indexnow_validate_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoThe IndexNow key (uses INDEXNOW_KEY env var if not provided)
hostYesThe hostname (e.g., example.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the tool fetches the hosted key file and compares contents, which implies a read-only network operation, but it says nothing about whether failures return errors or false, whether it can be rate-limited, or what permissions/network access are needed.

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 zero padding; the core action and the two validation criteria come first. Nothing in it is redundant with the title or schema.

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-annotation, no-output-schema validation tool, the description covers the essential mechanics. The main remaining gap is return semantics — whether the result is a boolean, a status object, or an error — which an agent would want for a check tool.

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 coverage is 100%, so both parameters are already documented, including the INDEXNOW_KEY env-var fallback and the hostname example. The description adds no additional meaning about how key and host interact or where the key file is expected to live.

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?

States a specific verb (validate) and resource (IndexNow key file), and specifies the two checks performed: file accessibility and key correctness. That clearly separates it from indexnow_generate_key and the submit_* tools, though it never names those siblings 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?

Usage is only implied — an agent can infer this is a pre-flight check before submitting URLs, but the description never says when to call it, whether it is required before submission, or what to do when validation fails. No alternatives or exclusions are stated.

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