Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

HTTP header checker

ayrank_http_headers
Read-only

Inspect response headers hop by hop, follow up to five redirects, and flag issues such as noindex tags, redirect chains, and temporary redirects without reading the page body.

Instructions

Use to list every response header of a URL hop by hop (redirects followed by hand, at most 5) and parse X-Robots-Tag, Link, Content-Type, Cache-Control, ETag, Last-Modified, Vary and Content-Encoding into issues such as noindex headers, redirect chains or temporary redirects. The body is never read. Headers are as seen from AY Rank's server; a CDN can answer differently by region or user agent.

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": "ayrank_http_headers"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to check, like https://example.com/page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing that redirects are followed manually with a cap of 5 hops, that the body is never fetched, and that results reflect AY Rank's server vantage point. The CDN/region/user-agent caveat is exactly the kind of limitation an agent needs to interpret results correctly.

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?

Two sentences, front-loaded with 'Use to', with no filler. The long list of parsed header names is dense but each item conveys real parsing scope, so it earns its space, though it could be trimmed slightly.

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

Completeness5/5

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

For a one-parameter read tool with no output schema, the description covers what is returned (headers plus parsed issues), the redirect handling, and the vantage-point caveat. Nothing an agent needs to call it or interpret results is missing.

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% and the single 'url' parameter is already documented with an example in the schema, so the baseline is 3. The description adds only indirect meaning (that the URL is fetched hop by hop with redirects followed), which is useful but not parameter-level detail.

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

Purpose5/5

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

States a specific verb and resource ('list every response header of a URL hop by hop') plus a second concrete function ('parse X-Robots-Tag, Link, Content-Type... into issues'). This clearly separates it from siblings such as ayrank_page_size or ayrank_broken_links, which operate on bodies or link graphs rather than headers.

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

Usage Guidelines4/5

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

Gives clear context for when the tool applies: header inspection and header-derived issue detection like noindex, redirect chains, and temporary redirects. It also implies a boundary by noting the body is never read, but it never names an alternative tool or states an explicit when-not condition.

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