Skip to main content
Glama

project_create

Destructive

Creates a new semantic circuit directory for Proteus projects without overwriting existing directories, so users can safely start new circuit work.

Instructions

Create a NEW semantic circuit directory; never overwrite existing directories.

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

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The description contributes one real behavioral fact beyond the annotations: creation is non-overwriting, so an existing directory is not clobbered. That is mild tension with destructiveHint=true, which implies a mutation with consequences the description never explains (e.g., whether a failed create leaves state behind). No contradiction, but the risk profile is under-described.

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 the action first and the key constraint second; no filler words and nothing redundant.

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 one-parameter creator with annotations covering the safety hints and no output schema, the definition is minimal but workable. It still omits what the parameter means, what is returned on success (path? handle?), and what happens on a name collision, which matter for calling it correctly first time.

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?

The schema has one required parameter with 0% description coverage, and the description does not compensate. It is unclear whether 'project' is a directory name, a path, or a project identifier, whether nesting is allowed, or what naming rules 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?

The definition names a specific verb ('Create') and resource ('semantic circuit directory') and adds an explicit scope marker ('NEW') that separates it from any read/overwrite behavior. It does not name a sibling such as project_open for existing projects, so differentiation is implied rather than stated.

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 phrase 'never overwrite existing directories' implicitly tells the agent this tool is only for non-existent targets, which is useful selection guidance. However, it never names the alternative path for already-existing directories (e.g., project_open/project_read), leaving the agent to infer the branch.

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