Omnara

List machines

machines_list

Read-onlyIdempotent

Lists the machines the caller can see, both BYO and pooled, newest first by default, with each one's connection state. Items are summaries without execution defaults or metadata.

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

Input Schema

Name	Required	Description
`name`	No	Case-insensitive glob over the list's logical name. `*` matches zero or more characters, `?` matches one character, and `\` escapes a wildcard.
`sort`	No	Sort order for named resources that expose created and modified timestamps.
`limit`	No	Maximum number of items to return in one page.
`orgID`	Yes	Organization ID (org_...).
`cursor`	No	Opaque pagination cursor from a previous response's next_cursor. Omit for the first page.
`source_kind`	No	Filter machines by source kind. Omit to include both BYO and pooled machines.
`machine_pool_id`	No	Return only machines provisioned by this machine pool.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026
- addedInput schema / properties / orgID / description
```
Added value: +"Organization ID (org_...)."
```

Changed1 schema field changedOct 14, 2026

addedInput schema / properties / machine_pool_id

Added value: +{
+  "description": "Return only machines provisioned by this machine pool.",
+  "pattern": "^mpo_[a-z2-7]{26}$",
+  "type": "string"
+}

First observedOct 13, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes further by disclosing the default sort ('newest first') and, importantly, that items are summaries lacking execution defaults or metadata - a real expectation-setting detail since there is no output schema. It does not discuss pagination behavior beyond what the cursor param implies.

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 with no filler; scope and default ordering are front-loaded and the payload caveat closes it out. Every clause earns its place.

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?

With no output schema, the description compensates by describing what each item contains (summary plus connection state, omitted execution defaults/metadata) and the default ordering. Missing only pagination/return-envelope detail, which is minor given the cursor parameter.

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%, so every parameter (name glob, sort, limit, cursor, source_kind, machine_pool_id, orgID) is already documented in the schema. The description only echoes the source_kind default ('both BYO and pooled') and the sort default, adding little beyond structured fields.

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+resource (lists machines) plus scope (the caller can see), coverage (BYO and pooled), default ordering, and the payload trait (connection state). An agent can distinguish it from machines_get and machines_create by the verb, though it never names a sibling explicitly.

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 reach for this versus machines_get for a single machine, or grant_machines_list for permission-scoped listings. Usage is only implied by 'lists ... the caller can see'; no exclusions or alternatives are offered.

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.