Skip to main content
Glama

discover_docker

Scans the local Docker environment to propose log sources per container and a detected Prometheus, returning configs ready to pass to create_source.

Instructions

Scan the local Docker environment and get a list of proposed sources (one per container's logs, plus a detected Prometheus). Each item's config is ready to pass to create_source.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses what is enumerated (container logs, Prometheus detection) and the shape of each result's config, but says nothing about access requirements (local Docker socket), whether the scan has any side effects, or how failures are reported.

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?

Two sentences, front-loaded with the action and result, followed by the actionable downstream hint. Every clause earns its place, including the parenthetical that explains the item count.

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 zero-parameter discovery tool with an output schema, the description covers what it does, what it returns conceptually, and how to use the result. The only meaningful omission is the environmental prerequisite (local Docker availability) that determines whether the call can succeed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to convey; the baseline of 4 applies. The description correctly spends no words on inputs.

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?

States a specific verb and resource ('Scan the local Docker environment') and precisely characterizes the returned value: a list of proposed sources, one per container's logs plus a detected Prometheus. The contrast with the creation step (config is 'ready to pass to create_source') makes the discovery-vs-creation distinction unambiguous.

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

Usage Guidelines4/5

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

It clearly establishes the workflow context: run this first, then feed each item's config into create_source. There is no explicit exclusion or prerequisite statement (e.g. Docker must be reachable locally), but the when-to-use condition is clear from the description alone.

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