Skip to main content
Glama

pilot_request_status

Read-onlyIdempotent

Read the state and result for a chat write request ID without operating the desktop, enabling status checks for pending or completed requests.

Instructions

Read the state and result for a chat write request_id (persistent when Rust is enabled) without operating the desktop. Unknown does not prove non-delivery in another process or before restart.

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": {
      "request_id": "<request_id>"
    },
    "name": "pilot_request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/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 meaningful behavioral context beyond annotations: persistence conditional on Rust being enabled, and the warning that an Unknown result does not prove non-delivery in another process or before restart. This is useful caveat information the agent would not otherwise get.

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?

Two sentences, front-loaded with the core purpose and followed by the important Unknown caveat. The parenthetical persistence note is slightly dense but earns its place; there is minimal wasted wording.

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?

For a read-only status query with no output schema, the definition explains what is being checked and includes a useful warning about Unknown results. However, it does not describe possible returned states or the result shape, and no output schema exists to carry that burden, leaving a meaningful gap for an agent interpreting the response.

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 description coverage is 0%, so the description must compensate for the single request_id parameter. It does this by identifying the parameter as a chat write request_id and noting the Rust persistence condition, which adds meaning beyond the bare string schema. It still does not explain the format or where the request ID comes from, so it stops short of full specification.

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: read the state and result for a chat write request_id, and distinguishes the operation from desktop interaction with 'without operating the desktop.' It does not explicitly distinguish itself from sibling chat tools like pilot_chat_wait or pilot_chat_read, so a 4 rather than a 5.

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 this is the tool for checking a chat write request without operating the desktop, which provides contextual usage guidance. It names no alternatives and gives no explicit when-not conditions beyond the Unknown caveat, so usage guidance is only implied.

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