Skip to main content
Glama
brynj-digital

laravel-forge-readonly-mcp

by brynj-digital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Site Logs

get_site_logs
Read-onlyIdempotent

Read a site's application, Nginx access, or Nginx error logs to diagnose failures; returns the end of the log by default, with optional tail length for more lines.

Instructions

Tail a site's logs: the Laravel/application log, or the Nginx access or error log. The first place to look when a site is throwing errors. Returns the END of the log by default (that is where failures are) — raise tail_lines for more. Requires the server:manage-logs scope, whose only write power is clearing logs. Note that Forge reads logs from the server over SSH at request time, so a server whose Forge access has been revoked returns an SSH error instead of a log.

Input Schema

NameRequiredDescriptionDefault
siteYesSite id from list_sites.
typeYesWhich log to read.
serverYesServer id the site is on.
tail_linesNoReturn only the last N lines, where failures appear (default 200). Output is additionally capped by character count, so a very long single line cannot flood the response.
organizationNoOrganisation slug. Optional when the server has a default configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / tail_lines
      Added value: +{
+  "description": "Return only the last N lines, where failures appear (default 200). Output is additionally capped by character count, so a very long single line cannot flood the response.",
+  "exclusiveMinimum": 0,
+  "maximum": 5000,
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover only the read/idempotent/safety profile; the description adds substantial context beyond them: the required server:manage-logs scope and its sole write power (clearing logs), the fact that logs are read over SSH at request time, and the specific failure mode when Forge access is revoked.

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?

Every sentence is front-loaded and earns its place: purpose, primary use case, default behavior with rationale, permission scope, and the SSH failure mode. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, 5-parameter tool with full annotations and no output schema, the description covers purpose, defaults, permissions, and operational caveats. 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains why the END of the log is returned by default (that is where failures are) and frames tail_lines as the lever to raise. It does not add syntax detail for site/server/organization beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Tail a site's logs') and enumerates the three log types (Laravel/application, Nginx access, Nginx error). This is concrete enough that an agent understands exactly what is retrieved without opening the schema.

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 a clear use context ('The first place to look when a site is throwing errors') and explains how to expand output via tail_lines. It does not, however, route the agent away from or toward the log-oriented siblings (get_deployment_log, get_background_process_log, get_server_event_output) or state when-not-to-use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools