Skip to main content
Glama

FrontierStack by Enfour, Inc.

Get fleet context

get_fleet_context
Read-onlyIdempotent

Return the selected Mac’s secret-redacted map of servers, roles, services, network locations and operating conventions, including the names of its linked servers.

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

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds genuine value beyond them by disclosing that secrets are redacted in the payload and that linked server names are included, which shapes what the agent can safely assume from the result. It stops short of saying anything about payload size or pagination.

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?

One dense sentence with no filler, and the returned-content list is front-loaded where the agent needs it. The enumeration is long enough to be slightly demanding to parse but every item earns its place as scope 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?

There is no output schema, so the description carries the return-value burden itself and does so by enumerating the returned categories and noting redaction and linked-server names. For a read-only, one-optional-parameter context fetch this is close to complete, with only response shape/size conventions absent.

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% and the single mac_id parameter is documented in-schema, including the 'optional only when exactly one Mac is online' rule. The description mentions the 'selected Mac' but adds no further meaning about how selection works or what happens if the id is omitted with multiple Macs online, so 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?

Uses a specific verb ('Return') with a concrete resource enumerated as 'servers, roles, services, network locations and operating conventions', which tells an agent exactly what it gets. It does not name or contrast itself with any sibling (e.g. get_server_health or list_frontierstack_macs), so the differentiation is left to inference.

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: describing the output as a 'map' of the fleet suggests an orientation/overview call rather than a targeted diagnostic. There is no explicit when-to-use, when-not-to-use, or named alternative, and the 'optional only when exactly one Mac is online' precondition lives only in the schema, not the description.

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.