Skip to main content
Glama

FrontierStack by Enfour, Inc.

Read scrubbed logs

read_logs
Read-onlyIdempotent

Read a bounded tail of a log on the selected Mac or a linked server. Secrets are removed before the text leaves the Mac.

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": {
      "source": "<source>"
    },
    "name": "read_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNoHow many lines from the end. Default 200.
mac_idNoOpaque id of one of this account's FrontierStack Macs. Optional only when exactly one Mac is online.
sourceYesWhich log: "os" (the system log), "wifi" (Wi-Fi events), a service name ("nginx", "apache", "mysql", "postgres", "redis", "sshd", "docker", "php-fpm", "postfix"), "vhost:example.com" for one website's access and error logs, "frontierstack" (the app's own log), or "path:/var/log/file.log".
targetNoOptional linked server, by the name or host FrontierStack knows it by, to run on over SSH. Omit for the selected Mac itself.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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."
    • changedInput schema / properties / target / description
      Previous value: -"Optional linked server (its name or host as shown in get_fleet_context) to run on over SSH. Omit for the selected Mac itself."New value: +"Optional linked server, by the name or host FrontierStack knows it by, to run on over SSH. Omit for the selected Mac itself."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the read-only, idempotent, and nondestructive annotations, the description discloses that retrieval is bounded and that secrets are removed before text leaves the Mac. The scrubbing statement is particularly valuable privacy context, although access and failure behavior are not discussed.

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?

Two short sentences front-load the action and scope, then state the important privacy behavior. There is no filler, and the compact wording remains informative.

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 this relatively simple read tool, the rich schema, safety annotations, bounded scope, and scrubbing disclosure provide enough context for correct invocation in typical cases. Because there is no output schema, the definition could still be more complete by indicating the returned text shape or how unavailable sources and SSH failures are reported.

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 schema already documents the line default and bound, Mac-selection condition, source forms, and SSH target behavior. The description's bounded-tail and local/linked-server wording usefully summarizes those semantics but adds little parameter-specific information beyond the schema.

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 states a specific operation and scope: reading a bounded tail of a log on either the selected Mac or a linked server. It clearly concerns general log retrieval, but does not explicitly differentiate itself from siblings such as diagnose or get_alert_errors.

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 implied as recent or bounded log inspection, with local-Mac and linked-server contexts identified. There is no explicit guidance about when to choose this tool over diagnostic, alert, or health-oriented siblings, nor any when-not guidance.

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.