Skip to main content
Glama
MCP Server Boilerplate

MCP Server Boilerplate

by jeandbonicel

File Operations

file-ops
Destructive

Read, write, and list files within a sandboxed .mcp-files directory using relative paths, enabling MCP workflows to manage local files inside a confined workspace.

Instructions

Read, write, or list files in a sandboxed directory (.mcp-files/). Paths are relative to the sandbox.

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": {
      "operation": "<operation>"
    },
    "name": "file-ops"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoRelative file path within the sandbox.
contentNoContent to write (required for write operation)
operationYesThe file operation to perform

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare this is not read-only, is not open-world, and is destructive. The description adds useful sandbox context by naming the .mcp-files directory and noting that paths are relative, but it does not explain what write destroys, whether existing files are overwritten, or how read/list failures appear.

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 two concise sentences with the operations and sandbox scope front-loaded. There is no redundant or filler wording.

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?

The definition is adequate for a three-parameter tool with complete schema descriptions and destructive annotations. However, for a multi-operation file tool with no output schema, it should clarify operation-specific behavior such as whether write overwrites or creates files and what read/list return.

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 100%, so the schema already documents operation, path, and content semantics. The description only adds the sandbox directory name and reinforces that paths are relative, which is marginal 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?

The description uses specific verbs and resource types ('Read, write, or list files') and names the sandbox scope. It does not explicitly distinguish this tool from sibling tools such as database or fetch-api, which keeps it below a 5.

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 implies this is the tool for sandboxed file operations, which gives adequate context for choosing it. It does not state when not to use it or point to an alternative for related tasks like database access.

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