maestro

by daniel-madrid-07

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_terminal_status

Check a terminal's live status by ID to see if it is idle, processing, completed, waiting for user input, or in error.

Instructions

Live status of one terminal: idle, processing, completed, waiting_user_answer, error.

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": {
      "terminal_id": "<terminal_id>"
    },
    "name": "get_terminal_status"
  }
}

Input Schema

Name	Required	Description	Default
`terminal_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Oct 21, 2026

TDQS

B3.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully enumerates the five terminal states and 'Live' implies the value is current at call time, but it says nothing about permissions, failure modes for an invalid terminal_id, or rate limits.

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 the key scope constraint ('one terminal') first and the state enumeration after. Nothing is wasted.

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?

The tool is simple (one required param) and an output schema exists, so return values need not be explained – though the state list partly duplicates it. What is missing is how to source terminal_id and any usage context, leaving the definition minimally viable.

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% – terminal_id has no description at all. The description only says 'one terminal' and never explains the id's format or where to obtain it (e.g., from list_sessions or launch_session), so it fails to compensate for the schema gap.

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+resource+scope ('Live status of one terminal') and enumerates the possible states, which lets an agent distinguish it from get_terminal_output (output text) and fleet_status (aggregate). It does not explicitly name any sibling, so it stops short of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of alternatives such as get_terminal_output or fleet_status, and no prerequisites. 'Live' hints at a polling/monitoring context but the agent must infer when this tool is the right choice.

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