Skip to main content
Glama
Sign In
LocalStack MCP Server

LocalStack MCP Server

by giovanemartins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

eventbridge_delete_rule

Deletes an EventBridge rule by name from LocalStack, with optional event bus specification. Removes the rule from your local AWS environment for testing.

Instructions

Delete an EventBridge rule from LocalStack

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "eventbridge_delete_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRule name
eventBusNameNoEvent bus name (default: default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing side effects like whether targets are removed, idempotency, or error behavior when the rule doesn't exist.

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?

The description is a single, concise sentence that immediately states the purpose without any filler or redundancy.

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

Completeness2/5

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

The tool has no output schema and no annotations, leaving the description as the only source of context. It omits key details such as return values, error conditions, and LocalStack-specific behavior, making it incomplete for an agent.

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% and both parameters have descriptions. The tool description adds no extra meaning beyond the schema, so the 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?

The description 'Delete an EventBridge rule from LocalStack' clearly states the action (delete) and the target resource (EventBridge rule). It distinguishes from sibling tools like eventbridge_delete_bus by specifying 'rule'.

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?

The description provides no guidance on when to use this tool versus alternatives, such as eventbridge_disable_rule or eventbridge_remove_targets. No prerequisites or consequences of deletion are mentioned.

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