laravel-forge-readonly-mcp

List Servers

list_servers

Read-onlyIdempotent

Lists servers in a Laravel Forge organisation with provider, region, size, PHP version, IP addresses, and provisioning status. Supports filtering and sorting to find a server ID for other tools.

Instructions

List the servers in an organisation — provider, region, size, PHP version, IP addresses and provisioning status. Supports filter/sort/include (try include="tags"). Use this to find a server id for the other tools.

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": "list_servers"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Comma-separated fields to sort by; prefix with "-" to reverse (e.g. "-created_at").
`cursor`	No	Pagination cursor from a previous response's meta.next_cursor.
`filter`	No	Field filters, e.g. {"name": "acme-web"}. Supported fields vary by endpoint.
`include`	No	Comma-separated relationships to embed (e.g. "tags,latestDeployment").
`page_size`	No	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.
`organization`	No	Organisation slug. Optional when the server has a default configured.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.0Oct 20, 2026

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
```

First observedv0.1.0Jul 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), so the description adds the returned field set and a concrete include relationship hint ("try include=\"tags\""). It does not discuss the 30-item page cap, but that is documented in the schema rather than left silent.

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?

Three tight sentences: resource + scope first, returned fields second, usage routing last. No filler, and the most decision-relevant information is front-loaded.

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 no output schema, the description usefully enumerates the fields returned, which is what an agent needs to judge relevance. Pagination semantics live in the schema, so the remaining gap is small.

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%, so filter/sort/include/cursor/page_size are already documented. The description restates filter/sort/include and adds a mild usage suggestion for include="tags", but no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 (list) and resource (servers) scoped to an organisation, and enumerates the fields returned (provider, region, size, PHP version, IPs, provisioning status). This cleanly separates it from the singular get_server sibling without needing to open either 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?

"Use this to find a server id for the other tools" gives an explicit routing purpose that points toward the id-consuming siblings. It stops short of naming a specific alternative or stating when-not to use it, but the intended context is clear.

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