Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

Alt text checker

ayrank_alt_text
Read-only

Audit a page's images for alt text status and flags like missing alt, unnamed image links, or filename alt text, without judging text quality or downloading images.

Instructions

Use to list a page's images (img, input type=image, area, svg role=img) with their alt text state: missing, empty, present or hidden, and flags such as missing alt, unnamed image links or file-name alt. It does not judge alt text quality and does not download images. Free AY Rank API, no key. JavaScript is not run, so content added by scripts is not seen.

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_alt_text"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint, openWorldHint) by disclosing that no API key is required, that JavaScript is not executed so script-injected images are invisible, and that image binaries are never fetched. These are exactly the behavioral facts that determine whether an agent can trust the result as complete.

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?

Front-loaded with the action, then layered limitations in short declarative sentences. Every sentence contributes a distinct constraint or output fact; nothing is restated from the title or schema.

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?

With no output schema, the description compensates by enumerating the returned alt-text states and example flags (missing alt, unnamed image links, file-name alt). For a one-parameter read-only checker, an agent has everything needed to call it and interpret the result.

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?

Single required parameter with 100% schema description coverage, so the schema already carries the meaning of 'url'. The description adds no format, normalization, or redirect-handling details beyond what the schema states, making the baseline 3 appropriate.

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+resource ('list a page's images') and enumerates both the element types covered (img, input type=image, area, svg role=img) and the output states (missing, empty, present, hidden). This is precise enough that an agent can distinguish it from every sibling audit tool without opening the schema.

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?

Explicitly bounds scope with negative guidance: it does not judge alt text quality and does not download images, which routes quality-assessment or asset-retrieval needs elsewhere. It also states prerequisite context (free AY Rank API, no key) and a key limitation (JavaScript is not run). It stops short of naming a specific alternative sibling, so a 4 rather than 5.

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