Skip to main content
Glama
Sign In
Maintenant

Maintenant

by kOlapsis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

get_container

Read-only

Retrieve detailed information about a specific container, including state, health, image, labels, and recent state transitions by container ID.

Instructions

Get detailed information about a specific container including state, health, image, labels, and recent state transitions.

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": {
      "container_id": "<container_id>"
    },
    "name": "get_container"
  }
}

Input Schema

NameRequiredDescriptionDefault
container_idYesInternal container ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds value by disclosing what the response contains, including the non-obvious 'recent state transitions' and 'health'. It does not mention behavior on an unknown or stale container_id, but that is a minor gap given the read-only annotation.

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?

A single front-loaded sentence with no filler; the field enumeration is dense, useful information rather than padding, and there is nothing to trim.

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 one-parameter read-only tool with no output schema, enumerating the returned fields is the right compensation and makes the tool callable without guessing. A note on identifier format or error behavior would close the remaining gap.

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?

There is a single parameter with full schema coverage, so the schema already explains container_id. The description adds only that the container is 'specific' and does not clarify whether a name, short ID, or full internal ID is acceptable, so it stays at the 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?

Specific verb ('Get') plus resource ('a specific container') with an explicit enumeration of the content returned: state, health, image, labels, and recent state transitions. It implicitly distinguishes itself from list_containers by scoping to a single container, though it never names that sibling.

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?

The singular 'specific container' implies this is a detail-lookup following a list operation, but no explicit when-to-use or when-not-to-use guidance is given, and no alternative (e.g., list_containers for browsing, get_container_logs for logs) is named.

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