Skip to main content
Glama

inspect_page

Inspect the currently opened page to capture viewport dimensions, landmarks, heading hierarchy, images, links, buttons, and forms with accessibility notices for frontend audits.

Instructions

Inspect the currently opened page, returning document/viewport dimensions, landmarks, heading hierarchy, images, links, buttons, and forms with accessibility notices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_itemsNoMaximum items to return in lists (default: 25)
include_hiddenNoWhether to include hidden elements (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 behavioral burden. It discloses that the tool inspects the current page and enumerates return categories, which implies a read operation, but it does not explicitly confirm read-only behavior, permissions, failure conditions, or output limits beyond what the schema states.

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?

The description is a single front-loaded sentence with no wasted wording. The list of returned categories is dense but each item contributes useful scope information.

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?

There is no output schema, so the description usefully compensates by listing the returned data categories and accessibility notices. The schema fully documents the two optional parameters, though the description still lacks explicit behavioral and alternative-selection guidance.

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 description coverage is 100%, so both max_items and include_hidden are already documented in the input schema. The description adds no further meaning about these parameters, so the baseline score 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?

The description states a specific verb and resource: inspect the currently opened page. It also enumerates the returned data categories, making the tool's scope clear, but it does not distinguish this broad inspection from siblings such as inspect_page_structure or inspect_element.

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?

The description supplies no explicit when-to-use guidance, prerequisites, or alternatives. It only describes what the tool does once invoked, leaving the agent to infer when this broad page inspection is preferable to the more focused inspect_* siblings.

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