Skip to main content
Glama
Sign In
Pi Desktop Bridge

Pi Desktop Bridge

by 0xHayd3n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

desktop_type

Destructive

Types text into the focused desktop app on a Raspberry Pi and returns a fresh screenshot so MCP clients can verify keyboard input.

Instructions

Type text into the focused desktop app and show a fresh screenshot.

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": {
      "text": "<text>"
    },
    "name": "desktop_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
capture_max_widthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=true, so the write/destructive profile is covered. The description adds the useful fact that a screenshot is captured after typing, but says nothing about irreversibility, focus prerequisites, or what happens on failure.

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?

A single front-loaded sentence with zero filler; the action and its observable effect are stated immediately.

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?

For a write tool with no output schema and fully undocumented parameters, the description does not explain the second parameter, focus prerequisites, or failure modes, leaving an agent under-informed despite the mention of the screenshot result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for 2 parameters, yet the description only implicitly covers the required 'text' and never mentions 'capture_max_width' at all. The description does not compensate for the documentation gap in the schema.

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?

Clear specific verb (type) plus resource (focused desktop app), and it names the side effect of returning a fresh screenshot. It is distinguishable from desktop_click or desktop_scroll, though it does not explicitly contrast with the closely related desktop_key tool.

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?

The phrase 'focused desktop app' implies a precondition (something must already be focused), but there is no explicit when-to-use vs. sibling guidance, no mention of needing a prior desktop_click/focus step, and no stated 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