Skip to main content
Glama
brynj-digital

laravel-forge-readonly-mcp

by brynj-digital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Deployments

list_deployments
Read-onlyIdempotent

Retrieve a site's deployment history with commit, author, status, duration and timestamps. Find when a site last shipped or identify a failed deployment to inspect further.

Instructions

A site's deployment history — commit, author, status, duration and timestamps. Use it to find when a site last shipped, or to identify a failed deployment to inspect with get_deployment. Newest first unless you pass sort (Forge's own default is oldest first).

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

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the description correctly focuses elsewhere and adds real behavioral context: default ordering is newest-first and this diverges from Forge's own oldest-first default. It doesn't mention pagination/auth details, but those are secondary for a safe read tool.

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 tightly written sentences, front-loaded with the resource and its returned fields, then routing guidance, then the ordering caveat. Every clause earns its place with no filler.

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?

With 100% schema coverage on all 8 parameters and no output schema, the description need not restate pagination, filter, or include semantics. It supplies the routing, the returned-field summary, and the ordering behavior an agent needs to call it correctly.

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 meaning the schema does not: it discloses the default sort direction and the underlying Forge default, which clarifies how the sort parameter behaves. That is a genuine semantic addition over the schema's mechanical 'comma-separated fields' description.

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 ('A site's deployment history') and enumerates the returned fields (commit, author, status, duration, timestamps). It clearly distinguishes itself from the sibling get_deployment by being the list/history view rather than a single record.

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?

Gives concrete contexts ('find when a site last shipped', 'identify a failed deployment to inspect with get_deployment') and explicitly names the alternative tool with the condition that selects it. It lacks an explicit when-not-to-use statement, so it falls just short of 5.

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