Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Reveal Machine Credentials

machine_credentials

Reveal a hosted machine's SSH, IPMI, or Grafana login only when the user asks, requiring confirmation before credentials are disclosed.

Instructions

Reveal one login of a hosted machine, as its console view shows it, only when the user asks for it. kind "ssh" is a shell on the host machine itself (host, port, username, password and the command), "ipmi" controls its power and console out of band, and "grafana" opens its metrics dashboard. machine is the machine_id from the machines tool. The account owner is emailed every time a login is revealed, and it needs a read & write key. With confirm=false (default) it only says what would be revealed and reveals nothing; call again with confirm=true after the user agreed. Give the login to that user and nobody else: never use it yourself or put it in files, commits or other tools. A login the machine doesn't have is credentials_not_available. 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

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_credentials"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNossh
confirmNo
machineYes
operation_idNo

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?

Goes well past the annotations: discloses the owner-notification side effect on every reveal, the read & write key requirement, the dry-run semantics of confirm=false, the credentials_not_available error, and that repeated confirmed calls execute again. The last point independently corroborates idempotentHint=false and adds the critical wrinkle that no operation record exists, so operation_status cannot audit the call.

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?

Front-loads the purpose and then layers safety, side effects, and error behavior in a logical order with no filler sentences. It is on the long side, but nearly every clause carries operational meaning; the one cost is that the kind breakdown interrupts the confirm-flow narrative.

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?

Covers the hard parts of a credential-reveal tool: authorization, notification, dry-run safety, idempotency, and error outcome, and an output schema means return shape need not be described. The residual gap is operation_id — its existence sits oddly against the statement that no operation record is kept, and the description does not reconcile the two.

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 coverage is 0%, so the description carries the full burden and does most of it well: kind's three values are explained behaviorally, confirm's two-phase meaning is spelled out, and machine's provenance is given. The fourth parameter, operation_id, is never mentioned, leaving an agent to guess what to pass or whether to omit it.

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 ('Reveal one login of a hosted machine'), scoped to console-view credentials, and immediately decomposes the resource into its three variants (ssh shell, ipmi power/console, grafana dashboard). An agent can tell this is about reading out machine logins, not source-repo or access-key credentials, without opening the 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?

Explicit when-to-use ('only when the user asks for it'), explicit two-phase protocol (confirm=false first to preview, then confirm=true after the user agrees), and explicit when-not ('never use it yourself or put it in files, commits or other tools'). It also names the machine identifier's origin (the machine_id from the machines tool).

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