Skip to main content
Glama

Page check

check_page
Read-only

Reads one page of the project's site the way Google and AI crawlers do, without JavaScript, and lists what holds it back: unreachable or noindex pages, content that only appears with JavaScript, missing title, description or headline, sitemap, AI crawler rules. Each finding comes with a ready-to-paste fix prompt. Free. url defaults to the homepage and must be on the project's domain. Pass keyword to check the title and headline against a search.

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": {
      "projectId": "<projectId>"
    },
    "name": "check_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
keywordNo
projectIdYes

Output Schema

NameRequiredDescriptionDefault
h1Yes
urlYes
titleYes
passedYes
statusYes
findingsYes
canonicalYes
schemaTypesYes
metaDescriptionYes
wordsWithoutJavaScriptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered; the description adds genuinely non-structured behavior — no JavaScript execution, live fetch of the customer's site, per-finding ready-to-paste fix prompts, and that the call is free (credit cost). That cost and fix-prompt behavior is context an agent could not get from any structured field.

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?

Front-loaded with the core action and finding list, then short sentences for defaults, cost, and the keyword option. The opening sentence is long and clause-stacked but every clause carries information; nothing is filler.

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?

With an output schema present, return values need no explanation, and the description still previews the shape (findings each with a fix prompt). Scope, defaults, domain restriction, cost, and the keyword option are all covered; only the behavior on a non-200 or off-domain URL is left unstated.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it does: url gets a default (homepage) and a domain constraint, and keyword gets both its purpose (title/headline checked against a search) and its optionality. projectId is only implicit ('the project's site'), which is the one gap.

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 (reads one page of the project's site) plus the exact scope and rendering model (as Google and AI crawlers see it, without JavaScript), and enumerates the finding categories. This is unmistakably a single-page crawler-perspective audit and is distinguishable from keyword- or performance-oriented siblings.

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 concrete operating context: url defaults to the homepage and must be on the project's domain, and keyword is the switch for title/headline search checking. It also flags cost ('Free'). It does not explicitly name which sibling to use instead for multi-page or keyword-volume checks, so routing guidance is clear but not exhaustive.

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