Skip to main content
Glama
Sign In
Linux MCP Server

Linux MCP Server

by Ronnietag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

file_write

Write content to files on Linux systems by specifying absolute paths and file content for file management operations.

Instructions

Write content to a file

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>",
      "content": "<content>"
    },
    "name": "file_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path
contentYesFile content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. 'Write' implies mutation but fails to specify destructive traits: overwrite behavior, directory auto-creation, encoding, or atomicity. Critical gaps for a file mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence of four words is front-loaded and efficient, but borders on under-specification given the tool's destructive potential and lack of annotations. Appropriately concise structure, yet insufficiently sized for the complexity.

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

Completeness2/5

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

Mutation tool with no annotations, no output schema, and undocumented behavioral edge cases (existing files, permissions). Description inadequate for safe agent operation; missing safety-critical context.

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 100% with clear descriptions ('Absolute path', 'File content'). Description adds no semantic detail beyond schema baseline, but schema adequately covers both required parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the verb (write) and resource (file) but provides minimal elaboration beyond the tool name 'file_write'. Does not differentiate from sibling 'file_read' or clarify write semantics (create vs overwrite).

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

Usage Guidelines2/5

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

Contains no guidance on when to use this tool versus siblings like 'file_read', or prerequisites like directory existence. No mention of overwrite behavior or error conditions.

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