Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

List Hosted Machines

machines
Read-onlyIdempotent

List hosted GPU hardware or retrieve one by machine_id to check status, GPU details, earnings, uptime, unread messages, clients, maintenance, disk warnings, fees, and optional live metrics.

Instructions

For users who host hardware on Meshive: list their machines, or show one by machine_id. Items include online status, GPU model and count, hourly earnings in USD, uptime rate (0..1) and unread_messages, the messages from the workspaces using the machine that the host hasn't read (read them with host_messages). One machine also shows clients: other users' workspaces that use it, with their pods and storage volumes (stopped ones too; a pod's ram_request is MiB, a volume's capacity_gb and available_size_gb are GiB and usage_rate is 0..1). Their workspace ids are what send_host_message takes. It also shows maintenance (every window with its id and status: upcoming, overdue, in_progress, done or expired), the schedules summary, the diagnostics boot_report and network_warnings, and fee (platform_fee as a fraction, 0.2 = 20%, and when a promotional fee ends). disk_warnings lists disk problems as kind, device, since, value and threshold: stall (the disk stopped responding, new workloads are paused and the machine is unlisted; the host checks the disk, then lists the machine again), slow (value is ms per write while the disk is lightly loaded) or full (the system disk /; value is percent used). slow and full leave the machine listed. Set include_metrics for a single machine's live CPU/RAM/GPU/network usage. In metrics, ram_size is bytes, the other sizes (ram_allocated, volume sizes, GPU vram_size) are MiB, and network_receive/network_transmit are bytes per second (x 8 / 1,000,000 for Mbps).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "machines"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
machineNo
include_metricsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, yet the description still adds real operational context: `stall` disk warnings pause new workloads and unlist the machine until the host re-lists it, while `slow`/`full` leave it listed, and `maintenance` statuses are enumerated. The main omissions are pagination behavior (`limit`/`cursor`) and whether `openWorldHint` implies any rate limiting or cost.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, but the body is a single dense block that spends most of its length on return-value semantics (units, enum meanings, cross-references) delivered as parenthetical fragments. Nearly every clause carries information, yet the volume is heavy for a list tool and would scan far better as a short purpose line plus a compact field-semantics list.

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

Completeness5/5

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

For a read-only listing tool with four params, the definition covers scope, both invocation modes, and deep domain semantics (unit conversions, `platform_fee` as a fraction, disk-warning kinds and their consequences, maintenance statuses). Combined with an existing output schema and read-only annotations, an agent has everything needed to call it correctly; only pagination semantics are absent.

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 0%, so the description must carry all four parameters. It explains `include_metrics` well and effectively describes the machine selector, but calls it `machine_id` while the schema property is `machine`, and never mentions `limit` or `cursor` at all — the two pagination params are left to convention.

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?

Opens with a specific verb and resource plus an audience constraint: 'For users who host hardware on Meshive: list their machines.' It also distinguishes the two modes (list all vs. show one by `machine_id`) and cross-references siblings (`host_messages` for reading messages, `send_host_message` for workspace ids), so an agent can separate this from `pods` or `workspaces` without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: this is for hosts, not workspace owners, and the single-machine mode is selected by supplying an id, with `include_metrics` explicitly scoped to 'a single machine's live CPU/RAM/GPU/network usage.' What's missing is any when-not guidance or explanation of when to prefer paging through the list versus fetching one machine, but the intended contexts are unambiguous.

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