Skip to main content
Glama
krusch-frontend-mcp

krusch-frontend-mcp

by kruschdev

generate_responsive_breakpoints

Read-onlyIdempotent

Generates standard CSS media queries for responsive breakpoints such as sm, md, and lg, with optional custom width overrides.

Instructions

Generates standard CSS media queries for responsive breakpoints (e.g. sm, md, lg) with optional custom width overrides.

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
customBreakpointsNoOptional overrides for breakpoints. e.g. { '3xl': '1920px' }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/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 safety and repeatability are covered. The description adds that a standard default set exists and that overrides are customized widths, but it never says whether customBreakpoints merge with or replace the defaults, nor what units/format the emitted CSS takes — meaningful gaps for a generator with no output schema.

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 sentence, front-loaded with the core action and artifact, with the optional-override caveat trailing where it belongs. No filler or redundant restatement of the tool name.

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 zero-required-parameter, single-optional-object tool with full schema coverage and annotations covering the safety profile, this is nearly sufficient — the agent knows what is produced and what can be overridden. The remaining hole is the result shape and default-vs-override merge behavior, which is undocumented anywhere.

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 parameter already carries an inline example ({ '3xl': '1920px' }). The description restates that overrides are optional custom widths but adds nothing about merge semantics, key naming rules, or accepted value formats beyond the schema's baseline.

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 pairs a specific verb ("Generates") with a specific artifact ("standard CSS media queries for responsive breakpoints") and gives concrete examples (sm, md, lg), which cleanly separates it from palette/style/variable generators among the siblings. It stops short of naming a sibling or explicitly distinguishing itself from generate_css_variables_from_figma or generate_component_styles.

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?

Usage is only implied: an agent can infer this is the tool for producing breakpoint media queries in a design-system pipeline, and that custom widths are optional. There is no explicit when-to-use statement, no prerequisite (e.g. tokens already ingested), and no exclusion pointing to an alternative tool for different casing or unit conventions.

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