Bot-Hosting.net

Write a file

files_write

Destructive

Create or overwrite a text file. A large file does NOT have to fit in one call: send the first part with mode 'overwrite', then the rest with mode 'append'.

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": {
      "id": "<id>",
      "path": "<path>",
      "content": "<content>"
    },
    "name": "files_write"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`mode`	No	'overwrite' (default) replaces the file. 'append' adds to the end, so a long file can be written across several calls instead of one huge one.
`path`	Yes	Volume-root relative, e.g. '/src/index.js' (the volume root is /home/container inside the container).
`content`	Yes	The text to write, as a string. A JSON object is accepted and stored stringified. Required - a call with no content writes nothing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known without the description. The description reinforces the overwrite behavior and adds a multi-call chunking strategy, but it doesn't warn that existing content is lost or explain failure/partial-write behavior.

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 sentences, zero filler, with the core action first and the large-file strategy second. Every clause carries information an agent can act on.

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 4-parameter mutation tool with no output schema, the description covers the main workflow but omits whether parent directories are created, what happens on partial failure, and permission requirements. Adequate but with clear gaps given the tool's destructive nature.

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 75% and the mode enum is already documented with the same append-for-large-files rationale. The description restates that workflow at a higher level rather than adding new syntax, defaults, or constraints beyond the schema.

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?

"Create or overwrite a text file" gives a specific verb pair plus resource, making the write/overwrite semantics explicit. It doesn't differentiate against siblings like files_edit or files_writeMany, but the operation itself is unambiguous.

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 description gives clear when-to guidance for one scenario: writing files too large for a single call, via overwrite-then-append. It says nothing about when to prefer files_edit or files_writeMany over this tool, so the routing guidance is only partially covered.

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

All Bot-Hosting.net tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?