Skip to main content
Glama

Create code tree

code_create

Create a code tree, empty or from the html starter (a page, a script and a stylesheet), whose files are its first change.

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>",
      "description": "<description>",
      "org": "<org>"
    },
    "name": "code_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.
nameYesLowercase letters, digits and hyphens.
titleNo
messageNoA brief note on the change.
starterNo
descriptionYesWhat the tree is for, in a sentence or two.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is covered. The description adds genuine context by explaining that the created files constitute the tree's first change, which tells the agent this operation also records a change entry. It does not mention permissions, defaults, or what happens to an existing name.

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; the creation modes and the first-change behavior are packed efficiently. Slightly dense parenthetical, but nothing is wasted.

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 six-parameter creation tool with no output schema, the description covers the core action and starter semantics but omits what is returned (tree identifier, branch, initial change id) and any preconditions. Annotations cover the safety profile, but the agent must still guess at the result of the call.

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 67%, so most parameters are documented structurally. The description adds meaning only to the 'starter' parameter (what the html starter contains) and implies 'empty' means omitting it; org, name, title, message, and description gain nothing beyond their schema text.

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 and resource ('Create a code tree') and clarifies the two creation modes: empty or from the 'html' starter with its page/script/stylesheet. This differentiates it from read/write siblings like code_tree or code_write, though 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 Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites (e.g., whether the org must already exist), and no statement about alternatives such as creating a tree via site_create or populating an existing tree with code_write. Usage must be inferred from the verb alone.

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