Hercules MCP

Overview Schema Source Related Servers Discussions Admin

workspace_write_file

Atomically write content to a file in the container workspace, rejecting unsafe paths. Accepts plain text or base64 content.

Instructions

Purpose: Atomically write content to a file in the owned container workspace. Constraints: Relative paths resolve under /opt/workspace; paths outside it and symlink/reparse escapes are rejected. Supply either content or content_base64, never both. mode defaults to 0644.… Example: workspace_write_file(path='targets.txt', content='http://host\n')

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": {
      "path": "<path>"
    },
    "name": "workspace_write_file"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No
`path`	Yes
`content`	No
`content_base64`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full transparency burden and does well by disclosing atomicity, path restriction, symlink/reparse escape rejection, content/base64 exclusivity, and default mode. It does not mention whether directories are auto-created or what the return value indicates, but the core behavioral traits are covered.

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?

The description is compact and well-structured with labeled sections for purpose, constraints, and an example. Every sentence adds value and there is no redundant repetition of schema information.

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?

Given the tool's simplicity and the presence of an output schema, the description is sufficiently complete for invoking the tool correctly. It covers path safety, content selection, and defaults, which are the main contextual details needed. Minor behavioral gaps remain, such as overwrite behavior and directory creation, but these are partially inferable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains path resolution, the mutually exclusive content/content_base64 parameters, and the mode default. The example also clarifies usage, though content_base64 is only implied rather than explicitly described.

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 writes content to a file in the owned container workspace, using a specific verb and resource. It distinguishes itself from the sibling workspace_read_file tool by focusing on the write operation.

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 provides clear context for when to use the tool, such as writing files in the workspace and respecting path constraints. It does not explicitly mention exclusions or alternatives, but the purpose and constraints make the intended use unambiguous.

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