Skip to main content
Glama
Sign In
Local MCP

Local MCP

by colibird-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

window_set_frame

Set a macOS window to exact position and size, ensuring consistent framing for repeated captures.

Instructions

Pins a window (by window_id) to fixed bounds {x,y,w,h} in global points, so every take is framed identicall...

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "window_set_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.336

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are present, and the description fails to disclose any side effects, prerequisites, or constraints (e.g., whether the window must be visible, what happens if bounds are invalid). This is a significant gap for a tool that modifies window state.

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

Conciseness2/5

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

The description is a single incomplete sentence. While concise, it fails to convey essential information, and the truncation indicates it is not well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's purpose (setting window frame) and the absence of an output schema, the description should explain prerequisites (e.g., how to obtain window_id) and the exact behavior. The current description is incomplete and provides minimal context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is empty, yet the description mentions 'window_id' and bounds {x,y,w,h} as parameters. This contradiction between the schema and the description provides no useful guidance. With zero parameters documented, the description adds no value beyond confusion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it pins a window to fixed bounds, which is a clear verb+resource action. However, the truncated ending and lack of differentiation from sibling tools like 'window_focus' reduce clarity.

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?

No explicit guidance on when or when not to use the tool. The mention of 'every take is framed identically' hints at use for consistent recording, but no alternative tools or exclusions are provided.

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

Deploy Server

Other Tools