Skip to main content
Glama
Sign In
agy_computer_use.mcp_server

agy_computer_use.mcp_server

by orakulzero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cu_find_anchor

Locates a template RGB icon on screen using SAD or NCC matching to identify its position for desktop automation.

Instructions

Locate template RGB icon on screen using pure Python SAD or NCC matching.

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": {
      "screen_rgb_base64": "<screen_rgb_base64>",
      "width": "<width>",
      "height": "<height>",
      "template_rgb_base64": "<template_rgb_base64>",
      "tmpl_width": "<tmpl_width>",
      "tmpl_height": "<tmpl_height>"
    },
    "name": "cu_find_anchor"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYesScreen pixel width.
heightYesScreen pixel height.
methodNoMatching method (SAD or NCC).
thresholdNoMatch threshold in [0.0, 1.0].
tmpl_widthYesTemplate pixel width.
tmpl_heightYesTemplate pixel height.
screen_rgb_base64YesBase64 encoded screen RGB bytes.
template_rgb_base64YesBase64 encoded template RGB bytes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that matching is pure Python, but says nothing about the return value (coordinates? score?), error behavior when no match is found, performance characteristics, or required input formats beyond the schema. That leaves important behavioral context undisclosed.

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 a single efficient sentence with no wasted words. The core action and matching methods are front-loaded.

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

Completeness2/5

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

The tool has eight parameters, six required, no annotations, and no output schema. The description omits the expected return format, the meaning of threshold behavior, and any method-selection guidance, which is not complete enough for an agent to invoke it confidently.

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?

Schema description coverage is 100%, so the schema already documents all eight parameters. The description adds no additional meaning beyond what the schema provides, making a baseline 3 appropriate.

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?

The description states a specific verb and resource: locating a template RGB icon on screen, using SAD or NCC matching. It is clear what the tool does, though the term 'anchor' is not defined and no sibling is named—none of the listed siblings appear to overlap directly, so differentiation is implicit rather than explicit.

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?

There is no guidance on when to use this tool versus alternatives, nor prerequisites such as whether the screen and template must be the same color space or scale. The method choice (SAD vs NCC) is mentioned but not explained or recommended for any condition.

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