Skip to main content
Glama
captenmasin

Laravel Cloud MCP Server

by captenmasin

Delete instance

laravel_cloud_delete_instance
Destructive

Permanently remove a Laravel Cloud instance by providing its ID and confirming the destructive operation.

Instructions

Delete an instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmYesMust be true to confirm this destructive operation.
instanceYesInstance ID.
Behavior3/5

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

Annotations already declare destructiveHint=true, so the description adds no extra context. The description neither contradicts nor enriches the behavioral cues provided by annotations.

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?

A single sentence with no filler. Extremely concise and front-loaded.

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

Completeness3/5

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

For a simple destructive operation with two parameters and clear annotations, the description is minimally adequate. However, it could mention the need for confirmation or prerequisites (e.g., instance existence).

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 fully documents parameters. The description adds no additional meaning beyond what the schema already provides.

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

Purpose4/5

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

The description 'Delete an instance.' clearly states the action and resource, but does not differentiate from other delete tools (e.g., delete_application, delete_environment) beyond the tool name.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., update_instance or stop_environment), prerequisites, or conditions like requiring the instance to be stopped.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/captenmasin/laravel-cloud-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server