Skip to main content
Glama
Sign In
windows2-mcp

windows2-mcp

by verisoft-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

is_element_displayed

Read-only

Check if a UI element is visible on screen using its element ID from find_element, ensuring the element is not off-screen or hidden.

Instructions

Check whether a UI element is visible on screen (not off-screen).

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": {
      "elementId": "<elementId>"
    },
    "name": "is_element_displayed"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementIdYesElement ID returned by find_element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, so description's behavioral burden is lower. Description adds that it checks on-screen visibility (not just existence), which is useful, but doesn't clarify if hidden/zero-size elements return false or error.

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?

Single sentence conveys complete purpose. No filler, no repetition of schema details. Perfectly concise.

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?

Given single parameter, full schema coverage, readOnlyHint, and no output schema, description is adequate. Could mention return type (boolean) since no output schema, but omission is minor.

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?

Schema has full description for elementId, so baseline is 3. Description reinforces that the elementId comes from find_element, adding context on tool chaining. This justifies a 4.

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?

Clearly states it checks UI element visibility on screen. Specifies 'not off-screen' to disambiguate from general display checks. Distinguishes from sibling tools like is_element_enabled or is_element_selected.

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?

Implies use for verifying visibility before interacting, but no explicit when-to-use or when-not-to-use guidance. No mention of alternatives among siblings like is_element_enabled or is_element_selected.

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