Skip to main content
Glama

rabbitmq-redis-stack-generator

invoke

Generate a production-ready docker-compose.yml for a multi-service infrastructure stack — messaging (Kafka/ZooKeeper, RabbitMQ, NATS), object storage (MinIO), search (Elasticsearch/OpenSearch), databases, caches, web servers and auth (Keycloak/Vault). Every service is health-checked, on a private bridge network, with named volumes and a matching .env.example. Kafka auto-wires its required ZooKeeper.

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": {
      "input": "<input>"
    },
    "name": "invoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesJSON request for this capability (the same body you'd send as an A2A message).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does well on output characteristics (every service health-checked, private bridge network, named volumes, matching .env.example, Kafka auto-wires ZooKeeper), but never states the basic operation semantics: does it return the YAML as text, write files to disk, overwrite existing files, require credentials, or have side effects? For a generator with a mutation-capable name and no readOnlyHint, that gap is significant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The output artifact is front-loaded in the first clause, followed by the coverage list and then the quality guarantees. Dense but every clause contributes concrete information; the service enumeration is long but functional rather than decorative.

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?

There is no output schema and no annotations, so the description must cover both behavior and contract. It thoroughly describes the generated artifact but leaves the request contract (the only parameter is an untyped JSON string) and the delivery mechanism unexplained, which is a real gap for an 'invoke'-style tool.

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 baseline is 3, and the description adds nothing about what belongs in the single opaque 'input' JSON string — no example fields, no service-selection or version-pinning hints. The agent learns what is generated but not how to specify it.

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 gives a specific verb+resource — 'Generate a production-ready docker-compose.yml' — and enumerates the covered stacks (Kafka/ZooKeeper, RabbitMQ, NATS, MinIO, Elasticsearch, databases, Keycloak/Vault), so the agent knows exactly what artifact is produced. The only weakness is the mismatch with the generic tool name 'invoke', which the description never reconciles (is this a docker-compose generator specifically, or a general dispatcher whose first documented capability is compose files?).

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

Usage Guidelines3/5

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

Usage is implied by the domain: reach for this when you need a multi-service local/dev compose stack. There is no explicit when-not guidance, no prerequisites (e.g. does it require a target directory or existing project?), and the sole sibling 'selftest' is unrelated so no routing is offered — leaving the agent to infer invocation conditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources