Skip to main content
Glama

Editorial column grid

bpj_design_column_grid
Read-onlyIdempotent

Find the column width for a page with asymmetric margins and equal intercolumn gutters.

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>",
      "left": "<left>",
      "right": "<right>",
      "columns": "<columns>",
      "gutter": "<gutter>"
    },
    "name": "bpj_design_column_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftYes
rightYes
widthYes
gutterYes
columnsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 clear. The description adds the computational constraint that margins are asymmetric and gutters are equal, but it omits return format, rounding behavior, and what happens when the column count does not divide evenly.

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 description is a single efficient sentence with the core constraint front-loaded. It contains no filler, though its brevity contributes to the missing parameter and output context noted elsewhere.

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?

This is a five-parameter calculation tool with no output schema, so the description should explain what is returned and how edge cases are handled. Instead, it only restates the input scenario and leaves the result semantics and calculation behavior undocumented.

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%, and although the schema titles provide parameter names and units, the description does not explain how the five parameters combine. It hints that left/right margins may differ and gutters are equal, but it does not clarify the formula, whether width includes margins, or how column count affects the result.

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 uses a specific verb ("Find") and resource ("column width") and adds a meaningful qualifier: asymmetric margins with equal intercolumn gutters. This distinguishes it somewhat from a generic baseline-grid calculation, though it does not explicitly name or contrast a sibling tool.

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 explicit guidance on when to use this tool versus alternatives such as bpj_design_baseline_grid or other layout calculations. The context of asymmetric margins and equal gutters is implied usage, not an instruction about when or when not to call it.

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.