Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Set block positions

set_block_positions

Pin components, terminal strips, or subsystems at specific x and y coordinates in a view to override auto-layout. Unpinned blocks keep positioning automatically, and wires reroute in the app.

Instructions

Pin blocks (components, terminal strips or subsystems) at positions in one view, instead of where auto-layout puts them. x, y are the block's top-left, relative to its own subsystem in that view (layout_view shows current values). Unpinned blocks keep laying out automatically. Wires reroute in the app.

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>",
      "blocks": "<blocks>"
    },
    "name": "set_block_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
blocksYes
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/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, non-destructive, closed-world mutation, so the description's job is to add operational context, which it does: coordinates are relative to the block's own subsystem in that view, and wires reroute in the app as a side effect. It leaves unclear whether re-pinning an already-pinned block overwrites or accumulates.

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?

Three short sentences with the core behavior front-loaded and no padding; the coordinate-frame explanation follows logically. The closing note 'Wires reroute in the app' is useful but slightly vague about timing.

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?

For a mutation tool with no output schema and only three parameters, this covers the essentials: what pinning means, the coordinate reference frame, view scoping, and the reroute side effect. Overwrite semantics on repeated pins and failure conditions are the main omissions.

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 only 33%, and x/y are bare numbers in the schema, so the description's explanation that they are the block's top-left relative to its own subsystem in that view is genuinely load-bearing. The subsystem and tag parameters are covered by schema descriptions, so the remaining gap is small.

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 states a specific verb and resource: pin blocks (components, terminal strips, subsystems) at explicit positions rather than auto-layout positions. It contrasts implicitly with auto-layout and references layout_view for current values, but never names clear_block_positions, the obvious sibling for undoing this, so differentiation is incomplete.

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 gives clear context for when to reach for this tool — you want blocks fixed at chosen coordinates instead of letting auto-layout decide — and notes that unpinned blocks continue to lay out automatically. It stops short of explicit when-not guidance or naming clear_block_positions as the way to revert a pin.

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