Skip to main content
Glama
Sign In
DeskPilot

DeskPilot

by iamtahiralvi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find

Locate UI elements by visible text or role—such as buttons, links, tabs, or menu items—using a lightweight lookup that falls back to OCR instead of a full snapshot.

Instructions

Find elements by visible text and/or role (button, link, edit, item, tab, checkbox, menuitem...). Falls back to OCR. Cheaper than a full snapshot.

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

Input Schema

NameRequiredDescriptionDefault
roleNo
textNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It discloses OCR fallback, supported role types, and relative cost, but omits read-only/side-effect status, matching semantics, result shape, and how the limit behaves.

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 dense sentences, front-loaded with capability, then fallback and cost. Every clause adds useful information and there is no filler.

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

Completeness3/5

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

There is no output schema and no annotations, so the description carries more burden. It covers the core behavior and fallback, but leaves return values, limit semantics, and safety status undocumented.

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 0%, so the description must define all three parameters. It partially explains role and text, but the limit parameter is never mentioned and it does not clarify whether matching is exact or substring.

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?

States a specific verb and resource: find elements by visible text and/or role, with a role vocabulary and OCR fallback. It also distinguishes itself from a full snapshot, though it does not specify what kind of handle or reference is returned.

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?

Positions the tool against a full snapshot on cost and mentions the OCR fallback, giving clear context for when to choose it. It lacks explicit exclusions or guidance versus siblings such as act or screenshot, so it falls short of a 5.

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