Skip to main content
Glama

push_into

Enter a container or inner shell from an SSH layer via docker exec or kubectl exec, inherit the execution pipeline, and set the new shell as the default layer.

Instructions

从默认层(或 from 指定层)进入内层 shell(docker exec -i sh / kubectl exec 等)——enter 管线全量继承追加(父层 docker→再 su 不丢)。新层成为默认层。需 ssh 层为源。

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": {
      "enter_cmd": "<enter_cmd>"
    },
    "name": "push_into"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNo源层名(缺省=默认层)
nameNo层名(缺省=label)
labelNo层显示标签
enter_cmdYes进入命令,如 "docker exec -i web sh"(别名 enterCommand/enter_command/enterCmd 等价)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavior burden and does disclose important traits: the new layer becomes the default layer, the enter pipeline fully inherits and appends so a parent docker layer followed by su is not lost, and an ssh-layer source is required. It does not cover failure or cleanup behavior, permissions beyond the prerequisite, or whether the entered shell is streamed or blocking.

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 compact and front-loads the main action and source-layer condition. The parenthetical inheritance note is dense but earns its place by explaining a non-obvious behavior.

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?

The description covers the prerequisite, the default-layer mutation, and inheritance semantics, which are material for this operation. It omits what entering the shell returns and how session or stream interaction works, which is a notable gap for a tool whose siblings include stream-related operations.

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 coverage is 100%, so the schema already documents all four parameters, including aliases and the enter_cmd example. The description only reinforces that `from` defaults to the default layer and adds no meaning for `name` or `label` beyond the schema.

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 states a specific action and resource: enter an inner shell from the default layer or a named source layer, using docker exec/kubectl exec. The requirement that the source be an ssh layer helps separate it from siblings such as push_ssh, but no sibling is named explicitly.

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 description supplies the prerequisite that an ssh layer must be the source and indicates the default and `from`-specified variants. It does not say when not to use this tool or name alternatives, so the agent must infer the choice from context.

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