Skip to main content
Glama
sassyconsultingllc

SassyMCP

Official
by sassyconsultingllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sassy_screen_info

Read-onlyIdempotent

Retrieves display configuration for all monitors, including bounds, DPI scale, and primary status. Use it before clicking or screenshotting to map absolute coordinates to the correct monitor.

Instructions

Read-only, takes no parameters. Returns the display configuration as JSON: every monitor with left/top/right/bottom/width/height, DPI scale_percent, and which is primary, plus a count. Uses native APIs on Windows (DPI-aware) and macOS (AppKit), falling back to a single-monitor pyautogui report elsewhere. Essential setup call for multi-monitor machines: run it before sassy_click or sassy_screenshot to translate absolute coordinates onto the right monitor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.1
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
-  "result": {
-    "title": "Result",
-    "type": "string"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"sassy_screen_infoOutput"New value: +"sassy_screen_infoDictOutput"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description adds value by detailing platform-specific behavior: 'Uses native APIs on Windows (DPI-aware) and macOS (AppKit), falling back to a single-monitor pyautogui report elsewhere.' This goes beyond the annotations, though it doesn't mention potential errors or edge cases.

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?

The description is well-structured, front-loading the read-only and no-parameters info, then output details, then platform and usage. It is concise but informative, with no wasted words, though it could be slightly tightened.

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

Completeness5/5

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

The description is complete for a no-parameter read-only tool. It specifies the output format, platform differences, and usage context. The output schema exists, so return format is fully defined. Annotations cover safety and idempotency, and the description adds the essential setup context.

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 tool has zero parameters, and the description confirms 'takes no parameters,' which aligns with the schema. Since there are no parameters, there is nothing more to explain, and the description appropriately states the absence without redundancy.

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 states the tool's purpose: 'Returns the display configuration as JSON' with specific fields. It distinguishes itself from siblings by noting it is a 'setup call' for multi-monitor machines before sassy_click or sassy_screenshot, which is distinct from other tools like sassy_desktop_state or sassy_shell.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'Essential setup call for multi-monitor machines: run it before sassy_click or sassy_screenshot.' It also explains the reason (translate absolute coordinates), giving clear context for when this tool is needed over alternatives.

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