Skip to main content
Glama

Create project

create_project

Create a new Mythex project and wake its sandbox

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": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
promptNoShort description used for naming

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, and closed-world. The description's useful addition is 'wake its sandbox', disclosing that creation also provisions/starts a sandbox — a side effect not encoded in annotations. It stops short of saying whether this is slow, costs resources, or what happens on repeated calls (relevant given idempotentHint=false).

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 wasted words. It is arguably terse to the point of under-specification, but nothing is redundant or buried.

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 two-parameter create tool with annotations covering the safety profile and no output schema to explain, the description is nearly sufficient: verb, resource, and the sandbox side effect are covered. Missing are return value expectations (e.g., a project identifier needed for follow-up calls like use_project) and any note on latency or required inputs.

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 only 50%: 'prompt' is documented in-schema while 'name' (maxLength 60) is not. The description adds no parameter meaning at all — it does not say what 'prompt' influences, whether 'name' is optional, or that zero parameters are required and defaults apply.

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?

States a specific verb ('Create') and resource ('a new Mythex project'), which separates it from siblings like get_project, delete_project, and update_project. However, 'Mythex' is never defined and no sibling is named as an alternative, so the differentiation is implicit rather than explicit.

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 when-to-use guidance, no prerequisites, and no mention of what to do if a project already exists or which sibling to prefer for other creation tasks. The agent must infer that this is the entry point for starting a new project purely from the name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources