Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Show Machine History

machine_history
Read-onlyIdempotent

Retrieve a hosted machine's downtime events and latest stress-test results—status, duration, logs, and performance samples—to diagnose uptime issues.

Instructions

Show a hosted machine's history; machine is the machine_id from the machines tool. kind "downtime" lists the state changes that count against its uptime (offline, not ready, a failed step), newest first: at most 20 events, from the last 90 days unless since/until (dates in YYYY-MM-DD, UTC) say otherwise. "stress_test" shows its latest stress test (stage, status, start, expected_duration_seconds and log) with its measured samples paged in items, oldest first. In a sample, gpuUtil, cpuUtil and fields ending in Pct are percentages, temperatures (gpuTemp, cpuTemp) are degrees Celsius, cpuFreq is the CPU clock in MHz, and gpuTflops and gpuComputingPower are the throughput that GPU (gpuId) reached under load, in TFLOPS.

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": {
      "machine": "<machine>"
    },
    "name": "machine_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNodowntime
limitNo
sinceNo
untilNo
cursorNo
machineYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which already declare this a read-only, idempotent, non-destructive, open-world operation), the description discloses result caps (at most 20 events), the 90-day default window, per-mode ordering (newest first for downtime, oldest first for samples), and pagination via `items`. It also documents units for sample fields, which is behavioral context an agent could not infer from annotations.

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?

Despite its length, every sentence is front-loaded and earns its place: purpose and `machine` first, then one block per `kind`, then the units reference needed because the schema has no field descriptions. No redundant restatement of the title or annotations.

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 two-mode history tool with six parameters at 0% schema coverage and an output schema present, the description supplies everything needed: mode semantics, date format, result bounds, ordering, and units. Return-value structure is covered by the output schema, so nothing material is missing.

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?

With 0% schema description coverage, the description carries the burden and mostly does: it defines `machine`, both `kind` values, `since`/`until` (YYYY-MM-DD, UTC, default 90-day window), and implies `limit` through the 20-event cap and `cursor` through paging. The `limit` and `cursor` parameters themselves are never explicitly described, leaving a small gap.

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 opens with a specific verb and resource ('Show a hosted machine's history') and immediately disambiguates the required `machine` argument as the machine_id from the `machines` tool, separating it from the sibling that lists machines. It then enumerates the two distinct modes of the tool, so an agent knows exactly what it retrieves.

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?

It clearly explains what each `kind` value is for: 'downtime' for state changes affecting uptime, 'stress_test' for the latest stress test with paged samples. There is no explicit when-not-to-use guidance or naming of an alternative tool for related data (e.g. activity), but the per-mode context is enough to select correctly.

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