Skip to main content
Glama
Systems Manager

Systems Manager

Get Host Record

sm_system_get_host_record
Read-onlyIdempotent

Retrieve a host record to get a stable host ID plus pending updates and uptime seconds for troubleshooting and update planning.

Instructions

Get host record (sm_system_operations). Returns an opaque stable host_id (never a hostname) with pendingUpdates and uptimeSeconds

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds useful behavioral context not present in structured fields: the returned host_id is opaque and stable, is never a hostname, and the record includes pendingUpdates and uptimeSeconds. It does not cover auth requirements, but the return semantics are a meaningful addition given there is no output schema.

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?

The description is two compact clauses with no filler. It front-loads the action and immediately specifies the returned identity and fields, so every phrase contributes information.

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?

For a simple zero-parameter getter with rich annotations and no output schema, the definition is nearly complete: it explains the return identity and two key fields. A small gap remains around when to prefer this over sibling system getters, but nothing critical for correct invocation 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?

The tool has zero parameters, so there is no parameter semantics for the description to explain. The baseline for a parameterless tool is 4, and the description appropriately does not fabricate parameter details.

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?

The description states a specific verb and resource ('Get host record') and clarifies the returned identity is an opaque stable host_id, not a hostname, plus two fields. This distinguishes it from pure uptime or network getters, though it does not explicitly name a sibling alternative.

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 when-to-use or when-not-to-use guidance. The description does not explain when an agent should call this instead of sm_system_get_uptime, systems_ingest_host, or other system getters, leaving selection to inference from the name alone.

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

Deploy Server

Other Tools