Skip to main content
Glama

runtime_status

Read-only

Reads running Proteus process, window, and menu metadata to report current application state. Use it to check what is open and active without capturing screenshots or emulating input.

Instructions

Read running Proteus process, window and menu metadata. No screenshots or input emulation.

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

Input Schema

NameRequiredDescriptionDefault
sessionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered by structured data. The description adds the useful scope note that no screenshots or input emulation occur, but says nothing about what metadata is returned, whether process/window/menu reads are cheap or blocking, or what happens when Proteus is not running.

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 short sentences, front-loaded with the core action and followed by a single scoping exclusion. No filler, no repetition of the tool name or annotations.

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, so the description is the only place a caller could learn what is returned, and it stays at the level of 'process, window and menu metadata'. Combined with the undocumented 'session' parameter and no failure-mode notes, it is minimally adequate rather than complete.

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?

The single parameter 'session' has 0% schema description coverage and the description never mentions it, so neither structured data nor prose explains what it does or whether omitting it targets the active session. The description therefore fails to compensate for the coverage 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 (Read) and a specific resource (running Proteus process, window and menu metadata), and explicitly excludes screenshots and input emulation. It does not name or distinguish itself from plausible siblings such as runtime_diagnostics or native_status, so an agent must infer the boundary.

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 negative clause 'No screenshots or input emulation' implies the tool is for metadata inspection only, which gives some selection signal. However, there is no explicit statement of when to use this versus runtime_diagnostics or the other status tools, and no prerequisites are given.

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