Skip to main content
Glama

kernline_page_summary

Read-only

Retrieve viewport details, frame information, and blocked stylesheet origins for an inspected browser tab to diagnose layout and CSS loading issues.

Instructions

Viewport, frames, and blocked stylesheet origins for an inspected tab

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

Input Schema

NameRequiredDescriptionDefault
tabIdNoBrowser tab id from kernline_list_tabs; omit when exactly one tab is connected

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.8/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a non-mutating read, lowering the burden on the description. The description adds the useful detail that the payload concerns viewport, frames, and blocked stylesheet origins — content the annotation does not cover. It does not disclose what happens with no connected tab, whether results are scoped to the active viewport, or any size/ordering behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact fragment with no filler, which is efficient. But the terseness comes at the cost of structure: there is no verb, no scope statement, and no front-loaded statement of what the tool is for, so brevity here edges toward under-specification.

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

Completeness3/5

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

For a one-optional-parameter, read-only tool this is close to adequate, and listing the returned categories partially compensates for the absent output schema. Still missing is any statement of when to reach for it and what the frame/stylesheet data is meant to diagnose, which an agent needs to choose it correctly.

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% and the single tabId parameter already documents its origin (kernline_list_tabs) and the omit-when-one-tab rule. The description adds no parameter meaning beyond that, which is the baseline case for complete schemas.

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

Purpose3/5

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

The phrase enumerates the returned data (viewport, frames, blocked stylesheet origins) for an 'inspected tab', so an agent can infer this is a read of page-rendering state. However, it is a bare noun phrase with no verb and no explicit statement that it reports diagnostics rather than modifying anything. It is distinguishable in topic from siblings like kernline_page_tokens or kernline_asset, but the differentiation is implied by noun choice rather than stated.

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?

There is no guidance on when to call this versus alternatives, no mention of prerequisites such as an inspected tab needing to exist, and no exclusions. The agent must infer usage entirely from the resource name and the sibling list.

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