Skip to main content
Glama
brynj-digital

laravel-forge-readonly-mcp

by brynj-digital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Organisations

list_organizations
Read-onlyIdempotent

Retrieve the slugs of Forge organisations accessible by the API token. Use this to find the organisation slug required by other Forge tools.

Instructions

List the Forge organisations this API token can reach, with their slugs. Every other tool takes an organisation slug (or uses the configured default). Start here if you do not know the slug.

Input Schema

NameRequiredDescriptionDefault
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.
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.

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.4/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 genuine value beyond that by disclosing the auth-scoping behavior ('this API token can reach') and the tool's role as a slug-discovery entry point. It doesn't discuss pagination, but the schema already documents 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?

Three short sentences, each load-bearing: what it lists, why the slug matters, and when to call it. Front-loaded with the action and completely free of filler.

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 a zero-required-param list tool with no output schema, the description conveys the essential return shape ('with their slugs') and its role in the workflow. It is slightly light on practical behavior like the implicit default-organization handling, 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 description coverage is 100%, so the schema already documents all five parameters (sort, cursor, filter, include, page_size) including the 30-item cap behavior. The description adds no parameter-level detail, so the baseline 3 applies.

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 (Forge organisations), with a clear scope qualifier ('this API token can reach'). The 'with their slugs' clause signals the return content, distinguishing it cleanly from all the get_/list_ resource siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent: 'Start here if you do not know the slug.' It also explains the downstream dependency ('Every other tool takes an organisation slug, or uses the configured default'), which tells the agent exactly when this tool is a prerequisite versus when it can be skipped.

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