Skip to main content
Glama

FrontierStack by Enfour, Inc.

List FrontierStack Macs

list_frontierstack_macs
Read-onlyIdempotent

List the FrontierStack Macs connected to this account, whether each is online, its app version, and its mac_id.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds value beyond them by disclosing the shape of the result (per-Mac online flag, app version, mac_id), which matters because no output schema exists; it does not cover pagination or empty-list behavior.

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 no filler: resource, scope, and returned attributes in one pass. Every clause earns its place.

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 zero-parameter read tool with no output schema, the definition covers the essentials: what is listed, the scope, and the key fields returned. Minor gaps remain — no hint about result size, pagination, or what an offline Mac implies — but nothing an agent needs to call it correctly 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 takes zero parameters, so the baseline is 4; there is nothing for the description to compensate for. It correctly avoids inventing parameters or filters that the schema does not expose.

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?

A specific verb (List) plus a specific resource (FrontierStack Macs) scoped to "connected to this account," and it names the attributes surfaced per Mac (online status, app version, mac_id). It does not explicitly distinguish itself from siblings, but those siblings (diagnose, read_logs, get_fleet_context) are obviously different operations, so the purpose is unambiguous.

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: an agent can infer this is the inventory/enumeration call whose mac_ids feed other tools, and the "connected to this account" phrasing implies scope. There is no explicit statement of when to use this instead of siblings like get_fleet_context, nor any stated prerequisite (e.g., what it means to be connected).

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.