Skip to main content
Glama

FrontierStack by Enfour, Inc.

Get server health

get_server_health
Read-onlyIdempotent

Read operational health from a selected FrontierStack Mac: services, monitors, disks, certificates and alerts it watches.

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

Input Schema

NameRequiredDescriptionDefault
areaNooverall (default): the Local Health board of everything the Mac monitors. queues: sanitized backlog counters for configured message brokers, streams, task queues and cloud queues (never message bodies).
mac_idNoOpaque id of one of this account's FrontierStack Macs. Optional only when exactly one Mac is online.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mac_id / description
      Previous value: -"Opaque Mac id returned by list_frontierstack_macs. Optional only when exactly one Mac is online."New value: +"Opaque id of one of this account's FrontierStack Macs. Optional only when exactly one Mac is online."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is given. The description adds a useful inventory of what health facets are reported, but says nothing about the mac_id online requirement or what a 'Local Health board' contains, which is the main behavioral gap.

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?

A single front-loaded sentence with the verb and target first, then the covered facets. No filler, though the colon list is dense and compresses five distinct domains into one clause.

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

Completeness3/5

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

For a low-complexity read tool with 0 required params and no output schema, this is close to adequate. It still leaves the agent guessing about the 'overall' vs 'queues' distinction and the single-online-Mac assumption, both of which only the schema covers.

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 coverage is 100% and the enum values are fully documented in the schema, so the description does no heavy lifting here. The phrase 'selected FrontierStack Mac' loosely echoes mac_id but adds no meaning beyond the schema's explanation of the optional-only-when-one-Mac-online rule.

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?

States a specific verb ('Read') and resource ('operational health') from a FrontierStack Mac, and enumerates the resource domains covered (services, monitors, disks, certificates, alerts). An agent can tell this apart from mutation siblings like service_action or replace_credential, though the boundary with diagnose/read_logs is not drawn.

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

Usage Guidelines3/5

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

Usage is only implied by 'read operational health' — a read-only health snapshot. There is no statement of when to prefer this over diagnose, read_logs, or get_alert_errors, and no prerequisite mentioned (e.g., that a Mac must be online).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.