Skip to main content
Glama
Nekoweb MCP Server

Nekoweb MCP Server

by Menal226

Write text file

nekoweb_write_file
DestructiveIdempotent

Writes complete text content to a Nekoweb site file, creating or replacing it, or editing an existing file. Use it for full HTML, CSS, or other UTF-8 text updates; partial edits are not supported.

Instructions

Write text content to a file on your Nekoweb site, creating it or replacing its entire content.

mode='create_or_overwrite' (default) uploads the file whether or not it exists; the parent folder must already exist (create it with nekoweb_create). mode='edit_existing' only changes a file that already exists.

Always send the complete new file content; there is no partial update. For binary or local files, use nekoweb_upload_file.

Examples:

  • "Change my homepage title" -> read it with nekoweb_read_file, then { path: "/mysite.nekoweb.org/index.html", content: "" }

  • "Add a stylesheet" -> { path: "/mysite.nekoweb.org/css/style.css", content: "body { ... }" }

Input Schema

NameRequiredDescriptionDefault
modeNo'create_or_overwrite' (default) writes the file whether or not it exists; 'edit_existing' fails if it doesn'tcreate_or_overwrite
pathYesPath from the account's file root, including the site folder, e.g. '/mysite.nekoweb.org/index.html'
contentYesThe complete new content of the file (UTF-8 text)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description is consistent with that while adding real context the annotations cannot convey: the whole file is replaced with no partial update, and a create_or_overwrite call fails if the parent folder is absent. It stops short of auth/scoping or rate-limit behavior, so it is strong but not exhaustive.

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?

Front-loaded with the action and the destructive full-replace warning, followed by mode rules, the cross-tool pointer, and two compact worked examples. Each sentence carries distinct information and nothing is repeated verbatim.

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?

For a three-parameter, two-required write tool with no output schema, the description covers overwrite risk, mode failure conditions, the prerequisite of an existing parent folder, and the correct sibling for non-text writes. An agent has everything needed to call it correctly.

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?

With 100% schema coverage the schema already documents all three parameters, including the mode enum values and the path example. The description restates mode behavior and the complete-content rule in slightly different words rather than adding new semantics, so it stays at the baseline rather than earning extra credit.

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 ("Write text content to a file") plus the exact write semantics: creates or fully replaces. It distinguishes itself from nekoweb_upload_file (binary/local files) and nekoweb_create (parent folders) by name, so an agent can route correctly without opening another 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?

Explicitly separates the two modes and their conditions: create_or_overwrite uploads regardless of existence, edit_existing only touches existing files. It also gives when-to-use alternatives in both directions -- nekoweb_create for the missing parent folder, nekoweb_upload_file for binary, nekoweb_read_file before editing a known file -- and closes with two concrete request examples.

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