Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Layout of a view

layout_view
Read-only

Computes the schematic layout for a project or subsystem view, listing block positions and sizes plus page frames. Use it to place blocks and pages without guessing.

Instructions

Run the schematic layout for one view (the project, or a subsystem's drill-down) and list every block's position and size and every print page's frame, so blocks and pages can be placed without guessing. Block x, y are relative to the block's own subsystem (what set_block_positions takes); ax, ay are absolute in the view (what pages use). Pages are a fixed 1504 × 800 frame; automatic pages (auto:0, auto:1…) cover whatever no placed page holds. Takes a few seconds, up to ~15 s on a large project.

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": {
      "project_id": "<project_id>"
    },
    "name": "layout_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
subsystemNoSubsystem whose drill-down view this is (name or id). Omit for the project view.
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint false, but the description adds real value on top: latency expectations ("a few seconds, up to ~15 s on a large project"), the returned structure (block position and size plus page frames), coordinate semantics (x, y relative to the subsystem, ax, ay absolute), and the rule for automatic pages. The only real gap is that it does not say whether the layout is deterministic or can change between runs.

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?

It is front-loaded with the action and its return content, and every clause carries information (coordinate frames, page size, automatic-page rule, runtime). It is dense rather than padded, though the parenthetical list of what coordinates feed into pushes it toward the long side for a single call.

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?

There is no output schema, so the description has to explain the return values, and it does: block positions and sizes, page frames, absolute and relative coordinates, and automatic pages. Combined with the latency hint and the coordinate semantics, this is close to complete for a two-parameter read tool.

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 coverage is 50%, and the schema already documents subsystem as the drill-down selector, so the description only deepens that meaning ("the project, or a subsystem's drill-down") and says nothing about project_id. With two parameters, this is the baseline: the description adds meaning to one parameter but not to the other.

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?

A concrete verb plus resource: "Run the schematic layout for one view" and "list every block's position and size and every print page's frame." It also distinguishes itself from the sibling set_block_positions by explicitly mapping block x, y to "what set_block_positions takes," so an agent can separate the read from the write without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly establishes the scope of a call (one view: the project, or a subsystem's drill-down) and connects block coordinates to set_block_positions, which implies the read-then-place workflow. It never states when not to use the tool or names an alternative for a different view, so the guidance is clear but not exhaustive.

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