Skip to main content
Glama

pilot_chat_read

Read-onlyIdempotent

Reads bounded text from a desktop chat or terminal accessibility tree and lists observed editable controls, helping inspect message and input areas for a specified app window.

Instructions

Read bounded text from a desktop chat or terminal accessibility tree; list observed editable controls. Region must be unique. Does not infer message authors.

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": {
      "app": "<app>",
      "from": "<from>",
      "max_chars": "<max_chars>"
    },
    "name": "pilot_chat_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes
fromYesend
regionNo
max_charsYes
window_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds useful behavioral context beyond that: text is bounded, editable controls are listed, regions must be uniquely matched, and message authors are not inferred. It still omits error behavior and return-shape specifics, but adds meaningful constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences, front-loaded with the core action and free of filler. It is slightly fragmented: 'Region must be unique' appears without explicitly tying it to the region parameter, which marginally reduces immediate clarity.

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 tool with five parameters, a nested region object, 0% schema description coverage, and no output schema, the description is too thin. It gives the core read purpose and a few behavioral limits, but leaves most parameter semantics and matching details unexplained, making it incomplete for correct invocation.

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%, so the description must carry the burden for five parameters. It only clarifies that text is bounded (relating loosely to max_chars) and that the region must be unique, while app, from, window_id, and the nested region role/name structure remain undocumented in both schema and description.

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: 'Read bounded text from a desktop chat or terminal accessibility tree' and adds a secondary action, 'list observed editable controls.' It implicitly distinguishes this read operation from sibling write/wait tools but does not explicitly name an alternative such as pilot_observe or desktop_get, so it stops short of full sibling differentiation.

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?

Usage is implied by the resource named: reading chat or terminal accessibility trees. The constraint 'Region must be unique' and the limitation 'Does not infer message authors' give some operational context, but there is no explicit when-to-use versus alternatives or when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.