Skip to main content
Glama

Baseline grid fit

bpj_design_baseline_grid
Read-onlyIdempotent

Find how many baselines fit after the first baseline offset with a fixed leading interval.

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": {
      "live": "<live>",
      "offset": "<offset>",
      "leading": "<leading>"
    },
    "name": "bpj_design_baseline_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
liveYes
offsetYes
leadingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the calculation is anchored at the first baseline offset with a fixed leading interval, but it does not say what exactly is returned (an integer count, a remainder, or a fit/no-fit flag) despite there being 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tightly written sentence with no filler and the key constraining clause front-loaded. It is efficient, though slightly dense in its phrasing ('after the first baseline offset with a fixed leading interval').

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?

For a three-parameter pure-computation tool with no output schema, the description conveys the core algorithm but leaves the return value and the role of the height input unstated. It is minimally sufficient, not complete.

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 the three parameters are only labelled by their schema titles. The description names two of them implicitly (offset, leading) but says nothing about the 'live' text-area height parameter, nor about the mm unit convention, so it does not compensate for the coverage gap.

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?

States a specific computation: counting how many baselines fit given a first-baseline offset and a fixed leading interval. The verb+resource (count baselines) is clear and the formula intent is visible, though it never distinguishes itself from the sibling bpj_design_column_grid or explains what the resulting number means.

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 guidance, no prerequisites, and no mention of alternatives such as the column-grid sibling. The agent must infer that this is the right tool for baseline-grid fitting purely from the name and the one-sentence description.

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.