Skip to main content
Glama

thanaton_create_project

Create a new project or application deployment target in Thanaton, defining its name, runtime, and internal port for subsequent deployments.

Instructions

Create a new project/application deployment target in Thanaton.

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

Input Schema

NameRequiredDescriptionDefault
nameYesProject name
slugNoOptional custom project slug
runtimeNoApplication runtime (default: nodejs)
app_portNoInternal HTTP listening port (default: 3000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a mutating create but says nothing about name-collision behavior, slug uniqueness, what happens if the runtime is unsupported, or what the tool returns on success.

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?

A single front-loaded sentence with no filler, and the key concept arrives immediately. It is efficient but borders on under-specified rather than padded.

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?

For a simple four-parameter creation tool with a fully described schema and no output schema, the description covers the essentials. However, with zero annotations and no return-value hints, an agent still cannot predict failure modes or what a successful creation yields.

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%, and the schema documents all four parameters including the runtime enum and defaults. The description adds only the framing that the result is a "deployment target," so the baseline 3 applies with little extra meaning contributed.

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 names a specific verb ("Create") and resource ("project/application deployment target"), which tells an agent exactly what the tool produces. It stops short of distinguishing this from sibling tools such as thanaton_list_projects or thanaton_deploy_code, so a 4 rather than a 5.

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?

There is no guidance on when to use this instead of alternatives (e.g. list_projects to check for an existing project, or deploy_code to push code afterwards), and no prerequisites such as required wallet/auth state. The reader must infer all usage context from the tool name alone.

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