Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Clear block positions

clear_block_positions
Destructive

Unpin all blocks in one view to return it to auto-layout while leaving other views' positions unchanged.

Instructions

Unpin every block in one view so it goes back to auto-layout. Other views keep theirs.

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": "clear_block_positions"
  }
}

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

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the description's added value is the blast radius: every block in exactly one view is affected while other views are untouched. That is precisely the context an agent needs before a destructive call. It stops short of saying whether the cleared positions are recoverable or what happens to locked blocks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two short sentences with the action and the scope stated first and the cross-view caveat second. No filler, no restatement of the tool name.

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 two-parameter destructive reset with no output schema, the description covers the action, the target scope, and the side-effect boundary. Only the irreversibility and any post-clear response are left unstated, which is minor given the annotations.

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%: the subsystem parameter is documented in the schema (including the 'omit for project view' rule), while project_id has no description anywhere. The description's 'one view' framing reinforces the subsystem/project-view distinction but adds no new detail about either parameter.

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 concrete verb and resource ('Unpin every block') plus the scope ('in one view') and the resulting state ('back to auto-layout'). It is clearly distinguishable from set_block_positions, though it never names that sibling as the inverse operation.

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 phrase 'so it goes back to auto-layout' implies when you'd want this (resetting a manually arranged view), and 'Other views keep theirs' bounds the effect. There is no explicit when-to-use statement or pointer to set_block_positions as the alternative for manual placement.

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