Skip to main content
Glama

pine_get_status

Retrieve the current emulator state to determine if it is running, paused, shutdown, or unknown.

Instructions

Get the current emulator state: 'running', 'paused', 'shutdown', or 'unknown'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition (inputSchema) for pine_get_status. No inputs required; describes returning one of 'running', 'paused', 'shutdown', or 'unknown'.
    {
      name: "pine_get_status",
      description: "Get the current emulator state: 'running', 'paused', 'shutdown', or 'unknown'.",
      inputSchema: { type: "object", properties: {} },
    },
  • Handler for pine_get_status: calls pine.getStatus() and returns the status string.
    case "pine_get_status": {
      return ok(`Status: ${await pine.getStatus()}`);
    }
  • src/tools.ts:171-175 (registration)
    The registerTools function (called from index.ts) sets up the ListTools/ CallTool request handlers that dispatch to the pine_get_status case.
    export function registerTools(server: Server, pine: PineClient): void {
      server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: TOOLS }));
    
      server.setRequestHandler(CallToolRequestSchema, async (req) => {
        const { name, arguments: args = {} } = req.params;
  • The getStatus() method on PineClient sends opcode 0x0F (Status) over the PINE protocol and decodes the u32 reply: 0→'running', 1→'paused', 2→'shutdown', else→'unknown'.
    async getStatus(): Promise<EmuStatus> {
      const r = await this.call(Op.Status);
      const s = r.readUInt32LE(0);
      return s === 0 ? "running" : s === 1 ? "paused" : s === 2 ? "shutdown" : "unknown";
    }
  • The EmuStatus type and Op.Status constant used by getStatus()
    async getStatus(): Promise<EmuStatus> {
      const r = await this.call(Op.Status);
      const s = r.readUInt32LE(0);
      return s === 0 ? "running" : s === 1 ? "paused" : s === 2 ? "shutdown" : "unknown";
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the possible return values, but omits behavioral traits like whether the tool is read-only, idempotent, or has side effects. The provided information is minimally adequate.

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, concise sentence that is front-loaded and contains no unnecessary words or information. Every part is relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description explains the return values adequately. It lacks details on error cases or state transition triggers, but for a simple status check tool, it covers the essential information.

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?

The tool has no parameters, and schema coverage is 100%. Per guidelines, 0 parameters baseline is 4. The description adds no parameter info, but none is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: retrieving the emulator state. It lists possible return values ('running', 'paused', 'shutdown', 'unknown'), which distinguishes it from sibling tools like pine_ping or pine_get_info.

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?

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, exclusions, or context for use, leaving the agent to infer its applicability.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dmang-dev/mcp-pine'

If you have feedback or need assistance with the MCP directory API, please join our Discord server