Skip to main content
Glama
Sign In
LocalStack MCP Server

LocalStack MCP Server

by giovanemartins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

eventbridge_list_targets

List all targets attached to an EventBridge rule in LocalStack. Specify the rule name and optional event bus to retrieve the configured targets for your local AWS infrastructure.

Instructions

List targets for an EventBridge rule in 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": {
      "rule": "<rule>"
    },
    "name": "eventbridge_list_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleYesRule name
eventBusNameNoEvent bus name (default: default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'List' implies a read-only operation, and LocalStack adds environmental context, but the description does not mention pagination, response format, or potential side effects. For a simple read-only tool, this is adequate but not richly detailed.

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, front-loaded sentence that conveys the essential information without any wasted words. It is concise and well-structured.

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 simple list tool with two parameters and no output schema, the one-sentence description captures the core purpose. However, it omits details about what a 'target' is, the return shape, or potential pagination, which could be useful. Overall, it is complete enough for a basic operation but leaves room for expansion.

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?

The input schema already provides descriptions for both parameters ('Rule name' and 'Event bus name (default: default)'), achieving 100% coverage. The tool description adds no extra parameter semantics, so the baseline score of 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 clearly states the action ('List targets') and the resource ('EventBridge rule'), making its purpose specific and unambiguous. It also differentiates from sibling 'eventbridge_list_rules' by targeting 'targets' rather than 'rules'.

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. It does not mention any prerequisites, exclusions, or suggest other tools for related operations, leaving the agent to infer usage context.

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