Skip to main content
Glama
julianbei

ARNO

by julianbei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

arno.create_file

Create a new file and any missing parent directories, refusing to overwrite existing files; use it when starting a file that does not yet exist.

Instructions

Create a brand-new file, and any missing parent directories. Refuses to overwrite an existing one — use replace_text or apply to modify existing content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFile path to create.
rootNoWorktree for this call. Default: the one set with workspace, else the start tree.
contentYesFile content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.17
    • changedInput schema / properties / root / description
      Previous value: -"Worktree of this repository to act in. Defaults to the session's workspace."New value: +"Worktree for this call. Default: the one set with workspace, else the start tree."
  2. Changed1 schema field changedv0.0.15
    • addedInput schema / properties / root
      Added value: +{
+  "description": "Worktree of this repository to act in. Defaults to the session's workspace.",
+  "type": "string"
+}
  3. Addedv0.0.12

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare destructiveHint=false; the description supplies the genuinely non-obvious behaviors — implicit parent-directory creation and a hard refusal on existing paths. It stops short of describing the failure mode (error vs. silent no-op) or encoding/permission requirements, which keeps it below a 5.

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?

Two tight sentences with zero filler; the create semantics are front-loaded and the exclusion/alternative routing follows immediately. Every clause earns its place.

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 simple create tool with no output schema, the description covers the essential behaviors an agent needs: parent creation, overwrite refusal, and alternatives. It omits the return value and error surface, which are minor gaps given the tool's simplicity.

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%, so path, root, and content are already documented by the schema. The description adds no format, encoding, or path-resolution detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('Create a brand-new file') plus a notable scope behavior ('and any missing parent directories'), so the agent knows this is a create-with-parents operation, not a plain write. It explicitly names the siblings that handle the mutation case (replace_text, apply), making it distinguishable from them without opening either schema.

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

Usage Guidelines5/5

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

Provides an explicit when-not condition ('Refuses to overwrite an existing one') and names the two alternative tools for modifying existing content. The routing rule for create vs. modify is fully spelled out with no inference required.

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