Skip to main content
Glama
Sign In
Code MCP Server

Code MCP Server

by agentics-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

generate_dockerfile

Generate a Dockerfile template for your project by specifying the programming language and optional framework for optimized container setup.

Instructions

Generate a Dockerfile template for a specific language/framework

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": {
      "language": "<language>"
    },
    "name": "generate_dockerfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageYesProgramming language for the Dockerfile
frameworkNoFramework-specific optimizations (e.g., alpine, express, fastapi)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only says 'Generate a Dockerfile template' but does not disclose whether it overwrites existing files, requires specific permissions, or has side effects. The agent cannot infer safety or expected behavior beyond the basic action.

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, well-formed sentence that is front-loaded with the key action and object. Every word is necessary and no filler is present.

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?

Given no output schema, the description should explain what the tool returns (e.g., file content, file path, or written file). It omits this crucial detail. Also, it does not clarify if the template is output to stdout or saved, leaving the agent guessing about follow-up actions.

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

Parameters2/5

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

Schema coverage is 100%, so the schema already explains parameters. The description adds no extra meaning beyond restating that it's for a specific language/framework. It does not provide constraints on valid framework values or examples, so it contributes negligible value.

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?

The description clearly states the action (generate), the resource (Dockerfile template), and the context (for a specific language/framework). It distinguishes from sibling tools like docker_build and docker_compose by focusing on template generation rather than execution or orchestration.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives is provided. The description does not mention prerequisites, scenarios where it's appropriate, or cases where other tools would be better, leaving the agent without decision support.

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