Skip to main content
Glama
Sign In
windy-word-mcp

windy-word-mcp

by sneakyfree
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

set_always_on_top

Toggle the Always on Top setting for the Windy Word window to keep it above other windows. Changes apply immediately and persist.

Instructions

Toggle whether the Windy Word window stays above other windows. Mirrors Settings → Appearance → Always on Top. Live update on the window + persist to appearance.alwaysOnTop. Idempotent.

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": {
      "on": "<on>"
    },
    "name": "set_always_on_top"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYestrue = pin above all, false = normal Z-order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A4.5/5.0
Behavior5/5

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

In the absence of annotations, the description fully discloses key behavioral traits: it applies live updates to the window, persists the change to 'appearance.alwaysOnTop', and states idempotency. This provides an agent with a clear understanding of the tool's effects.

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?

The description is concise with three sentences front-loading the core action. Every sentence adds value: purpose, mapping to settings, and behavioral notes. No extraneous information.

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?

Given the tool's simplicity (single boolean parameter, no output schema), the description covers all necessary aspects: purpose, behavior, persistence, and idempotency. It is complete for an agent to correctly invoke the tool.

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?

The input schema already provides a clear description for the only parameter. The tool's description does not add additional semantic information about the parameter beyond what the schema states, so the score remains at the baseline for full schema coverage.

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 uses a specific verb 'Toggle' and clearly identifies the resource 'Windy Word window'. It further explains the effect (stays above other windows) and distinguishes itself from siblings by being a unique window management function.

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 provides a clear usage context by referencing the equivalent setting ('Mirrors Settings → Appearance → Always on Top'). It implicitly guides when to use this tool, though it does not explicitly state when not to use it or mention 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