Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Get Host Install Command

host_install_command

Generates a time-limited command that installs the Meshive agent on a new machine and registers it to your account. Requires confirmation before the secret command is issued.

Instructions

Get the command that installs the Meshive agent on a new machine and registers it to the user's account, like the console's Add machine: agent_type "compute" for a GPU or CPU machine, "storage" for a storage machine. For about 10 minutes, whoever has the command can register machines to this account, so it is a secret. The account owner is emailed each time one is issued. With confirm=false (default) it only says what it is and issues nothing; call again with confirm=true after the user agreed. Run it only on the machine the user named, as root, and only when they asked you to; otherwise give it to that user alone. Never put it in files, commits or other tools. The machine shows up in the machines tool once its agent connects. The server keeps no operation record of this call, so operation_status can't look it up and a repeated confirmed call runs again.

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": "host_install_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
agent_typeNocompute
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.8/5.0
Behavior5/5

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

Adds context well beyond the annotations: a roughly 10-minute validity window, the secret-handling obligation, the owner email on each issuance, that the machine appears in the machines tool only after the agent connects, and that no operation record is kept so a repeated confirmed call executes again. That last point reinforces the non-idempotent hint with a concrete consequence.

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?

Purpose and scope are front-loaded, followed by the security constraint and the confirm protocol; nearly every sentence carries operational weight. It is dense and runs long, and the security obligations are interleaved with mechanics rather than grouped, but there is little true filler.

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?

An output schema exists, so return values need no explanation. For a secret-issuing, side-effecting call, the description covers validity window, leakage risk, confirmation protocol, run location, and non-lookupability — everything an agent needs before invoking it.

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?

Schema description coverage is 0%, so the description must carry the load; it does explain confirm's default and two-step behavior and enumerates agent_type values beyond the schema's bare default ('compute' for GPU/CPU, 'storage' for storage). operation_id is never named, though the note that no operation record is kept implicitly covers it, 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?

States a concrete verb and object ('Get the command that installs the Meshive agent on a new machine and registers it to the user's account') and anchors it to a familiar console action. It also scopes the agent_type values, so an agent can tell this apart from machines or operation_status 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 Guidelines5/5

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

Gives explicit when-to-use and when-not-to-use rules: run only on the machine the user named, as root, and only when they asked; otherwise hand the command to the user alone. It also prescribes the two-step confirm=false then confirm=true flow gated on user agreement.

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