Designers

Logo size rules

logo_size_rules

Read-only

Compute logo clear space and minimum sizes. Give width and height (any unit, pass unit), optionally letterform (height of a capital or the x-height in the same unit), kind (wordmark, lockup, symbol, monogram) and clearSpaceMultiple (default 1 letterform). Returns clear space on each side, the total exclusion zone, a compact clear space (half), minimum height and width for screen (smallest letterform 8 px) and print (1.5 mm), and a size table for common widths marking where the logo falls below the minimum. If letterform is omitted it is estimated and the result says so. The floors are conventions; your brand guide may differ.

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": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "logo_size_rules"
  }
}

Input Schema

Name	Required	Description
`kind`	No	wordmark, lockup, symbol or monogram
`unit`	No	Unit of width, height and letterform, e.g. px, mm. Default px
`width`	Yes	Logo artwork width
`height`	Yes	Logo artwork height
`letterform`	No	Height of a reference letterform (capital or x-height), same unit
`clearSpaceMultiple`	No	Clear space as a multiple of the letterform, 0.25 to 4. Default 1

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly annotations, the description discloses concrete outputs: clear space per side, total exclusion zone, compact clear space, screen and print minimums, and a size table. It also warns that omitted letterform is estimated and that floors are conventions, giving the agent useful behavioural caveats.

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?

The leading sentence states the core purpose, then parameters, then returns, then caveats. It is fairly long but every clause carries information; the caveat about conventions is appropriately placed at the end.

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

Completeness5/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 compensates by enumerating the return fields and the screen/print minimums. All six parameters receive some explanation, and the fallback estimation behaviour is disclosed, leaving little ambiguity for an agent to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning: letterform is defined as a capital or x-height in the same unit, clearSpaceMultiple is stated as 0.25–4 with a default of 1, and unit is framed as accepting any unit. This goes beyond the terse schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Starts with a specific verb and resource: 'Compute logo clear space and minimum sizes.' It is immediately distinguishable from sibling logo_contrast_variants, which addresses colour rather than sizing geometry.

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 context makes the purpose clear but the description never states when to reach for this tool versus alternatives, nor any exclusions. There is no explicit routing guidance such as naming a sibling; usage is implied rather than prescribed.

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

All Designers tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?