Skip to main content
Glama

Responsive image planner

plan_responsive_images
Read-only

Plans responsive images. Pass breakpoints as min-viewport:width pairs such as 0:100vw, 768:50vw, 1200:600px (vw or px), and optionally dprs (default 1,2), sourceWidth (original pixel width, upscaled candidates are dropped), format (jpeg, webp, avif, png; default webp), aspect (16:9 or 1.5, adds a height for layout stability), urlPattern containing {w}, aboveFold (true adds fetchpriority high and no lazy loading), maxViewport (default 1920) and content (photo, graphic or noisy). Returns the srcset widths (thinned so neighbors differ by at least 18 percent, max 8), the sizes string, an tag, and a rough byte estimate from typical bits per pixel for the format. Estimates are within about 2x either way. It plans markup; it does not resize files.

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": {
      "breakpoints": "<breakpoints>"
    },
    "name": "plan_responsive_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
dprsNoComma-separated DPRs, default `1,2`.
aspectNoWidth:height such as 16:9.
formatNo
contentNo
aboveFoldNo
urlPatternNoURL with {w}, e.g. /img/hero-{w}.webp
breakpointsYesPairs like `0:100vw, 768:50vw, 1200:600px`.
maxViewportNo
sourceWidthNoOriginal image width in pixels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotation only covers safety (readOnly, non-destructive). The description adds substantial behavioral detail absent from structured fields: the returned artifacts (thinned srcset widths with an 18% gap, max 8 candidates, sizes string, <img> tag, byte estimate), the accuracy caveat (~2x), and the no-resizing limitation.

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 required parameter and compact, with each clause carrying useful information. The single dense paragraph of parameter notes is slightly harder to scan than a structured list, which keeps it from a 5.

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?

For a read-only planning tool with no output schema, the description covers outputs, accuracy, and all parameter behaviors, which is nearly complete. The remaining gap is the lack of explicit routing guidance relative to sibling planning tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 56%, the description compensates well by explaining semantics for every parameter: breakpoint pair syntax, dprs default, sourceWidth dropping upscaled candidates, format default, aspect adding a height, urlPattern's {w} placeholder, aboveFold effects, maxViewport default, and content choices.

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 specific verb and resource ('Plans responsive images') and the closing sentence clarifies the boundary ('It plans markup; it does not resize files'). It does not explicitly contrast itself with close siblings like plan_breakpoints or plan_asset_exports, so it falls short of a 5.

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 scope note 'It plans markup; it does not resize files' helps an agent understand the tool's boundary, but there is no explicit when-to-use guidance or named alternative for tasks like choosing breakpoints or exporting assets.

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