Skip to main content
Glama

FrontierStack by Enfour, Inc.

Get alert delivery errors

get_alert_errors
Read-onlyIdempotent

List outstanding alert and report delivery errors (email, Slack, SMS, push and similar) with likely causes and fixes.

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

Input Schema

NameRequiredDescriptionDefault
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuine value by stating that results come with likely causes and fixes, and that only outstanding errors are returned.

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?

A single front-loaded sentence with the resource first and the channel scope immediately after; no filler and nothing buried.

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 one-optional-param read tool with full annotations and no output schema, the description is nearly sufficient: it says what is returned (errors plus causes and fixes). Ordering/pagination and the online-Mac prerequisite are left to the schema.

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%, so mac_id is fully documented in the schema, including its conditional-optionality rule. The description adds nothing about the parameter, so the baseline 3 applies.

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?

Clear verb and resource: "List outstanding alert and report delivery errors", with the channels enumerated (email, Slack, SMS, push). An agent can distinguish this from health/diagnostics siblings, though no sibling is named explicitly.

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?

"Outstanding ... errors" implies the situation to use it (delivery failures that haven't cleared), but there is no explicit when-to-use versus when-to-use-alternatives guidance, and no exclusions.

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.