Runcrate

Check instance status

instance_status

Read-onlyIdempotent

Check the live status of an instance. Syncs with the provider.

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": {
      "id": "<id>"
    },
    "name": "instance_status"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Instance ID
`workspace`	No	Workspace ID (optional: defaults to the authenticated workspace)
`environment`	No	Environment name (optional: defaults to the environment this session acts in)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026

removedInput schema / properties / env

Removed value: -{
-  "description": "Environment name (optional — defaults to main)",
-  "type": "string"
-}

addedInput schema / properties / environment

Added value: +{
+  "description": "Environment name (optional: defaults to the environment this session acts in)",
+  "type": "string"
+}

changedInput schema / properties / workspace / description

Previous value: -"Workspace ID (optional — defaults to authenticated workspace)"New value: +"Workspace ID (optional: defaults to the authenticated workspace)"

First observedOct 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. 'Syncs with the provider' hints that the call reaches out to the provider and may be slower or return fresher data than a cached read, but it is too vague to say whether it mutates provider state, incurs latency, or can fail on provider errors.

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 short sentences with the core action front-loaded and no filler. The second sentence is fragmentary and its subject ('syncs') is ambiguous about what is being synchronized, keeping it just short of a 5.

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 simple three-parameter read with no output schema, the description is minimally adequate. However, it gives no indication of what status information is returned or how a 'syncing' state might affect the response, which is the main thing an agent needs to interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including explicit defaults for workspace and environment, so the schema carries parameter meaning. The description adds nothing beyond it, which meets the baseline for full-coverage schemas.

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: check the live status of an instance. It is clear what the tool does, but it never distinguishes itself from the sibling get_instance, which an agent would reasonably consider interchangeable with this one.

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 guidance on when to prefer this over get_instance, list_instances, or get_request, and no prerequisites or exclusions are given. The agent must guess from the name alone.

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

All Runcrate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.