Skip to main content
Glama

generate_responsive_breakpoints

Read-onlyIdempotent

Generate mobile, tablet, and desktop responsive layout specs at 375px, 768px, and 1440px breakpoints to standardize component layouts.

Instructions

Generate 375px (mobile), 768px (tablet), and 1440px (desktop) responsive layout specs.

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

Input Schema

NameRequiredDescriptionDefault
component_typeNogrid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the concrete output contract (three fixed widths with device labels), which is genuinely useful beyond annotations, but says nothing about how component_type changes behavior or what a 'spec' contains.

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?

A single front-loaded sentence with the key output values (375/768/1440 and their device labels) stated immediately. No filler, nothing to trim.

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?

With no output schema, the description does well to enumerate the three breakpoints, but it leaves the shape of a 'layout spec' undefined and the lone parameter unexplained. For a one-param generator that is mostly adequate, though an agent still can't predict the return structure.

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

Parameters2/5

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

Schema description coverage is 0% for the single parameter component_type, and the description never mentions it. So the only input an agent can vary is completely undocumented in both places, leaving the caller to guess its accepted values and effect (the default 'grid' hints at a taxonomy the description ignores).

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 names a specific verb ('Generate') and resource ('responsive layout specs') and enumerates the exact breakpoints produced, so an agent knows precisely what comes out. It doesn't explicitly contrast with the nearest sibling (generate_color_palette), but the resource noun is different enough to disambiguate.

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 statement of when to reach for this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer usage purely from the resource name.

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