Skip to main content
Glama
brynj-digital

laravel-forge-readonly-mcp

by brynj-digital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Site Command History

list_site_commands
Read-onlyIdempotent

Retrieve the audit history of commands run from a site's Commands panel, including who ran them and when. Read-only; does not execute commands.

Instructions

The history of commands run from a site's Commands panel, with who ran them and when. An audit read — this cannot run a command.

Input Schema

NameRequiredDescriptionDefault
siteYesSite id from list_sites.
sortNoComma-separated fields to sort by; prefix with "-" to reverse (e.g. "-created_at").
cursorNoPagination cursor from a previous response's meta.next_cursor.
filterNoField filters, e.g. {"name": "acme-web"}. Supported fields vary by endpoint.
serverYesServer id the site is on.
includeNoComma-separated relationships to embed (e.g. "tags,latestDeployment").
page_sizeNoItems per page, at most 30. Forge caps pages at 30 and silently returns 30 for anything larger, so read the "page" line and follow the cursor.
organizationNoOrganisation slug. Optional when the server has a default configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / page_size / description
      Previous value: -"Items per page (Forge default 30)."New value: +"Items per page, at most 30. Forge caps pages at 30 and silently returns 30 for anything larger, so read the \"page\" line and follow the cursor."
    • changedInput schema / properties / page_size / maximum
      Previous value: -100New value: +30
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds real value by confirming execution is impossible and by describing the returned content (who ran each command and when), which goes beyond the structured fields. It omits pagination behavior, but the schema covers that in detail.

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, front-loaded sentences with zero filler. The purpose comes first and the key safety constraint follows immediately.

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?

With 8 parameters, nested filter object, pagination, and no output schema, the description gives enough to understand content and safety, and the schema fully covers parameter mechanics. It could be slightly richer about pagination or filterable fields, but nothing critical is missing.

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 coverage is 100%, so every parameter, including the page_size cap and cursor semantics, is documented in the schema. The description adds only that results are ordered by run time/who, without explaining sort, filter, or include usage. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('history of commands run from a site's Commands panel') and immediately disambiguates it from command-executing or output-fetching siblings with 'this cannot run a command'. An agent can distinguish this audit-list from get_command_output or background-process tools 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 Guidelines3/5

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

The phrase 'An audit read — this cannot run a command' tells the agent when-not to expect execution, which is useful negative guidance. However, it never names when to choose this over get_command_output or other command-related siblings, leaving the primary usage decision implicit.

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