Skip to main content
Glama
Senpai-Sama7

SDLC Command Center MCP Server

by Senpai-Sama7

Write File (Gated)

sdlc_write_file
Destructive

Create, overwrite, or append UTF-8 text files with approval gating, automatic backups, and audit logging. Use the returned changeId to roll back changes.

Instructions

Create/overwrite/append a UTF-8 text file. Dry-run unless confirm=true; backs up existing content; appends to the audit log; rollback via the returned changeId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNooverwrite
pathNoTarget directory. Filesystem roots are rejected; UNC/network paths require an explicit environment override.
dryRunNoExplicit dry-run switch. Mutation only occurs when dryRun is false AND confirm is true.
confirmNoApproval gate. Without confirm=true the call is a dry-run and changes nothing.
contentYesUTF-8 content (max 1 MiB).
filePathYesFile to act on, relative to the target directory (absolute paths contained by it are accepted).
allowSensitiveNoRequired to touch .env/key/credential-style paths.
expectedSha256NoOptional optimistic-concurrency guard: current file SHA-256.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
changeIdNo
Behavior5/5

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

Annotations already mark destructiveHint=true, but the description adds crucial behavioral details: backup creation, audit log append, and rollback via changeId. These go beyond annotations and fully disclose the tool's side effects and safety mechanisms.

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 concise sentences capture the entire tool behavior without fluff. The information is front-loaded, mentioning modes, dry-run, backup, audit, and rollback in order of importance. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, 2 required, output schema exists, 17 siblings), the description covers all critical behavioral aspects: gating, backup, audit, and rollback. It does not need to repeat schema info or explain output structure. The description is self-sufficient for correct usage.

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 high (88%), so the description adds little extra meaning. It reinforces the dry-run logic but does not enhance understanding of individual parameters beyond what the schema already provides. The description does not compensate for the missing mode description or other minor gaps.

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?

The description clearly states the tool creates/overwrites/appends UTF-8 text files, distinguishing it from read-only and replace siblings. It specifies the dry-run behavior, backup, audit logging, and rollback capability, leaving no ambiguity about its core function.

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

Usage Guidelines4/5

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

The description explains the gated nature (confirm=true required for mutation) and the dry-run default. While it does not explicitly compare with siblings like sdlc_replace_in_file, the context of file creation vs. targeted replacement is implicit. A brief when-not-to-use statement would elevate it to 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Senpai-Sama7/autonomous-sdlc-command-center'

If you have feedback or need assistance with the MCP directory API, please join our Discord server