Skip to main content
Glama

native_status

Read-only

Reads simulation commands, logs, modal dialogs, and state through a version-pinned Qt bridge, with optional Frida inspection and no input emulation.

Instructions

Read commands, logs, modal dialog and simulation state via version-pinned Qt function bridge. Optional Frida; no input emulation.

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": {
      "session": "<session>"
    },
    "name": "native_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare a safe, closed read, so the description's value is in the extra detail: it works through a version-pinned Qt bridge, Frida is optional rather than required, and it deliberately performs no input emulation. Those traits meaningfully constrain what the agent can expect. It stops short of saying what happens when Frida is unavailable or how expensive the call is.

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 terse sentences, front-loading what is read and following with mechanism and constraints; nothing is wasted. The compression is close to telegraphic, though, and a few extra words on 'session' would have cost little.

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?

Annotations cover the safety profile and there is no output schema to explain, so the remaining burden is small. Still, for a tool that returns live simulator state, the description gives no hint of result shape or of what 'session' refers to, leaving the only required input unexplained.

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 required parameter 'session' has 0% schema description coverage and is never mentioned in the description. With no explanation of what a session identifier is or how to obtain one, the description leaves the only input undocumented in both places.

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 enumerates the resources it returns: commands, logs, modal dialog, and simulation state, plus the underlying mechanism (a version-pinned Qt function bridge). It does not differentiate itself from near-neighbors such as native_read, native_inspect, or runtime_status, so an agent cannot tell from the text alone which of these to pick.

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?

"Optional Frida; no input emulation" implies this is for passive observation rather than driving the UI, which is a usable usage signal. However, it never states when to prefer this over native_read or runtime_status, and gives no prerequisites or exclusions beyond that one clause.

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