Skip to main content
Glama
Sign In
mcp-osascript

mcp-osascript

by m0rvayne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_displays

Retrieves details about all connected displays, including position, size, and main display designation, for effective multi-monitor window management.

Instructions

Get information about all connected displays — position, size, and which is the main display. Useful for multi-monitor window management.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. 'Get information' clearly signals a read-only operation, and the description discloses the scope and contents of the result. It does not state permissions or edge cases, but for a simple no-parameter query this is acceptable.

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 concise sentences with no filler. The main action and output content are front-loaded, and the use case is provided in a single additional clause.

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 no-parameter, read-only tool, the description gives enough context to understand what will be returned. There is no output schema, but listing the key fields partially compensates. Exact formatting or units are not specified, but they are not essential for correct invocation.

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?

The input schema has zero parameters, so the baseline is 4. The description adds value by explaining what output information is meaningful (position, size, main display), even though there are no parameters to document.

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?

The description clearly identifies the resource ('all connected displays') and the specific information returned (position, size, and main display). This makes the tool easy to distinguish from sibling tools like manage_windows or screenshot.

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?

The description includes a clear usage context: 'Useful for multi-monitor window management.' It does not explicitly name alternatives or when-not-to-use cases, but the no-parameter read-only nature and the context provided are sufficient for a tool like this.

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