Skip to main content
Glama

FrontierStack by Enfour, Inc.

Control a supported web service

service_action
Destructive

Check, start, stop or restart one supported Homebrew web service on the selected Mac. status is read-only; stop and restart interrupt the service. Changes run only if the owner allowed changes on that Mac, and may wait for the owner's approval there.

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": {
      "name": "<name>",
      "action": "<action>"
    },
    "name": "service_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe Homebrew service.
actionYesstatus only reads; the others change the service.
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

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds genuinely new behavioral facts: the permission gate on the target Mac, the possibility of waiting on owner approval, and which actions interrupt service availability. It does not describe failure behavior, whether a rejected approval errors or returns pending, or what state the service is left in after an interrupted stop.

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?

Three short sentences, front-loaded with the action set and resource, followed by the read-only vs interrupting distinction, then the permission caveat. Every sentence carries distinct information with no repetition of the title or schema.

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 3-parameter tool with full schema coverage and annotations present, the definition covers action semantics, side effects, and authorization preconditions. The main remaining gap is the return shape for status, since no output schema exists and the description never says what the check reports.

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 description coverage is 100%, with both enums enumerated and mac_id's conditional optionality already documented in the schema. The description adds only the phrase 'the selected Mac', which lightly reinforces mac_id's role but contributes no syntax or constraint detail beyond the schema; 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?

The description opens with a specific verb set (check, start, stop, restart) and a narrowly bounded resource (one supported Homebrew web service on the selected Mac), so the agent knows exactly what the tool operates on. It does not, however, contrast itself with any sibling such as diagnose or get_server_health, leaving differentiation to inference from the sibling names.

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

Usage Guidelines4/5

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

It gives clear per-action context: status is read-only, stop and restart interrupt the service, and all changes require the Mac owner to have allowed changes and may block on owner approval. It stops short of explicit when-not guidance or naming an alternative tool for read-only inspection, but the conditions for safe use are well stated.

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.