Skip to main content
Glama

query_design_rules

Read-onlyIdempotent

Retrieve typography, contrast, spacing, and layout rules from the design system store so agents can apply consistent, compliant styling decisions.

Instructions

Retrieve typography, contrast, spacing, and layout rules from the design system store.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.2/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 without the description. The description adds only the content scope (which rule categories live in the store); it does not disclose how filtering behaves, whether an empty query returns everything, or anything about result shape.

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 no filler; the resource and its domain coverage come first and nothing is wasted. Its brevity is a virtue at the sentence level even though the overall definition is thin.

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

Completeness2/5

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

For a two-parameter retrieval tool with 0% schema coverage and no output schema, the description omits the essentials an agent needs: what 'query' accepts, whether parameters are optional and what happens when they are omitted, and roughly what comes back. Annotations cover safety but not calling mechanics.

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 0% for two parameters, so the description must carry meaning. It partially does: 'typography, contrast, spacing, and layout' plausibly map to the values of the category parameter, which is useful signal. However the 'query' parameter is never explained — free text, keyword, or identifier — leaving half the parameter surface undocumented.

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 ('Retrieve') and resource ('design rules') and enumerates the covered domains: typography, contrast, spacing, layout. That is enough to distinguish it from generation siblings like generate_color_palette or generate_responsive_breakpoints. It stops short of explicitly differentiating itself from those siblings, so it is clear but not maximally differentiated.

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 when-to-use or when-not-to-use guidance and no named alternative. Implicitly an agent would call this when it needs existing design constraints rather than generating new ones, but that inference is left entirely to the reader.

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