Omnara

Get machine

machines_get

Read-onlyIdempotent

Returns one active machine's full record: connection state, execution defaults (secret IDs only, never values), metadata, and the latest failure report. Machines in other lifecycle states, such as pool machines still provisioning, aren't returned.

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": {
      "machineID": "<machineID>",
      "orgID": "<orgID>"
    },
    "name": "machines_get"
  }
}

Input Schema

Name	Required	Description	Default
`orgID`	Yes	Organization ID (org_...).
`machineID`	Yes	Machine ID (mch_...).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026
- addedInput schema / properties / machineID / description
```
Added value: +"Machine ID (mch_...)."
```
- addedInput schema / properties / orgID / description
```
Added value: +"Organization ID (org_...)."
```
First observedOct 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds real value on top: secrets are surfaced as IDs and never values (a privacy guarantee), the latest failure report is included, and non-active lifecycle states are excluded from results. It stops short of saying what happens when the target machine isn't active (error vs empty).

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 tight sentences, zero filler, with the returned payload front-loaded and the scoping caveat following as a qualifier.

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?

There is no output schema, so the description's enumeration of returned fields does the necessary work and covers the important non-obvious one (secret IDs, not values). The only gap is failure behavior for a non-active or nonexistent machine, which an agent must guess.

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% and both required parameters (orgID, machineID) carry their own patterns and descriptions, so the schema fully carries parameter semantics. The description adds no syntax or constraint detail beyond that, making the baseline 3 correct.

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?

States a specific verb and resource ('Returns one active machine's full record') and enumerates the payload: connection state, execution defaults, metadata, latest failure report. The singular 'one machine' plus the active-only scope cleanly separates it from machines_list without needing to name the sibling.

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 description implies when this is appropriate by limiting results to active machines, and notes that provisioning/pool machines won't come back. However, it never names an alternative (e.g. machines_list to discover IDs, or how to inspect non-active machines), so the agent must infer routing from context alone.

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

All Omnara 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.