Skip to main content
Glama

observable-backend-stack-generator

invoke

Generate a production observability stack as docker-compose: Prometheus (scrape config + alert rules), Grafana (provisioned datasource + dashboard), Alertmanager and node-exporter. Add db/cache images and it emits the FULL observable backend stack (services + Prometheus exporters, pre-scraped) with a .env.example.

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.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose substantial output behavior: Prometheus scrape config and alert rules, Grafana provisioning, Alertmanager, node-exporter, pre-scraped exporters, and .env.example. However, it does not say whether the tool writes files or returns text, whether it overwrites existing files, or what side effects occur.

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 description is front-loaded with the main action and output, and the component list is useful rather than wasteful. It is somewhat dense but remains appropriately sized for the capability.

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 input is a freeform JSON string, and the description does not explain the expected JSON request shape for this capability. With no output schema and no annotations, the definition is missing key invocation details even though it describes the generated stack well.

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 generic input parameter is already documented in the schema. The description adds no detail about the JSON request body or which fields control db/cache image inclusion, so it does not meaningfully exceed the schema baseline.

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, "Generate," and a concrete resource, a production observability stack as docker-compose, with named components. It is clear what the tool produces, though it does not clarify the generic "invoke" name or differentiate from the sibling selftest tool.

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?

It implies usage by explaining that adding db/cache images expands the generated stack to a full observable backend. It does not state when not to use it, prerequisites, or alternatives; with only selftest as a sibling, that gap is modest but still present.

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