Skip to main content
Glama

inspect_breakpoints

Probe responsive layout changes across viewport widths from 320px to 1920px to reveal navigation shifts, grid/column changes, and declared CSS @media queries.

Instructions

Inspect how layout transforms across viewport widths (320px to 1920px). Probes navigation shifts, grid/column count changes, and discovers declared CSS @media queries.

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

Input Schema

NameRequiredDescriptionDefault
key_widthsNoWidths to test (default: [320, 480, 640, 768, 1024, 1280, 1440, 1920])
inspect_css_media_queriesNoInspect document stylesheets for CSS @media rules (default: true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it does disclose the inspection dimensions (navigation shifts, column counts, media queries), which is meaningful behavior. However, it does not state whether the tool mutates viewport state, how long a multi-width sweep takes, or what form the findings take, all of which matter for an unannotated probing tool.

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?

Two tight sentences with the scope (viewport range) front-loaded and the probed behaviors listed immediately after. There is no filler, hedging, or repetition, and every clause contributes information about what gets measured.

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 two-optional-parameter, read-style inspection tool with no annotations and no output schema, the description covers what is measured but not what comes back — whether results are per-width diffs, a list of matched media queries, or a summary. That omission leaves the agent unable to anticipate the response shape.

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%, with both optional parameters documented in-schema including the default width list, so the baseline of 3 applies. The description's '320px to 1920px' range roughly echoes the default key_widths and its '@media queries' mention maps to inspect_css_media_queries, but it adds no semantics beyond those already stated in the schema.

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?

States a concrete verb and resource ('Inspect how layout transforms across viewport widths') and enumerates what is probed: navigation shifts, grid/column count changes, and declared CSS @media queries. It is clearly about responsive layout measurement, though it never names how it differs from near siblings like test_responsiveness, compare_viewports, or inspect_element_responsiveness.

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

Usage Guidelines3/5

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

The use case (checking layout behavior across a 320px–1920px range) is implied clearly enough to guide selection, but there is no explicit when-to-use/when-not, no mention of prerequisites such as a page being open, and no routing to alternatives. The agent must infer the boundary against the responsiveness-related siblings.

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