Skip to main content
Glama

Layven

by io.layven

write

Idempotent

Create or replace a file. Inline content up to 1 MiB; use request_upload for larger. Pass expected_version to fail instead of overwriting concurrent changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFile to create or replace, relative to the workspace root. Parent folders are implicit.
contentYesFull new content of the file. Replaces the current content entirely.
encodingNoHow content is encoded. Use base64 for binary.utf8
mime_typeNoContent type, e.g. text/markdown. Guessed from the extension when omitted.
workspaceNoWorkspace slug. Optional, defaults to "temp".
override_lockNoWrite even if another agent holds a lock on this path. Recorded in the activity log.
expected_versionNoFail with VERSION_CONFLICT unless the file is currently at this version. Omit for last-write-wins.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior1/5

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

Annotations include destructiveHint=false, but the description explicitly says 'replace a file' and 'overwrite concurrent changes,' which are destructive behaviors. This is a direct contradiction with the annotation, so the score is 1 despite the useful size and concurrency details.

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?

Three short sentences front-load the core purpose and then add key usage constraints. No filler, repetition, or unnecessary details.

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?

The description covers purpose, size threshold, and concurrency behavior, while the 7-parameter schema with per-parameter descriptions handles the remaining details. It differentiates from sibling tools effectively, though it omits return behavior and lock specifics.

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 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema: the 1 MiB inline limit and the conditional use of expected_version to produce a VERSION_CONFLICT, while 'replace' reinforces the full-content semantics.

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 starts with 'Create or replace a file,' a specific verb+resource statement that clearly identifies the tool's function. It distinguishes itself from sibling tools like edit, delete, and request_upload by emphasizing creation/replacement and large-file handling.

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 states to use request_upload for content larger than 1 MiB, providing a clear alternative. It also instructs passing expected_version to fail on concurrent changes, giving actionable when-to-use guidance.

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

All Layven toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct operation: file CRUD (write, read, edit, delete), versioning (history, restore), search (grep, list with q), locking (lock, unlock), uploads (request_upload, finalize_upload), and activity tracking. Even similar tools like request_upload and finalize_upload are complementary rather than overlapping.

Naming Consistency4/5

Tool names are lowercase and action-oriented, with single-word verbs (read, write, delete) and two compound verbs (request_upload, finalize_upload) following a verb_noun pattern. This is consistent enough to be predictable, though the mix of single words and compound words is a minor deviation.

Tool Count5/5

14 tools is well-scoped for a versioned file management server. Each tool covers a necessary aspect of the domain—file operations, version control, search, locking, uploads, and activity—without unnecessary bloat or missing critical functionality.

Completeness5/5

The tool set covers the full lifecycle of file management: create/write, read, edit, delete, restore, list, search, lock, unlock, upload/download (via request_upload/finalize_upload and read's download URL). The only potential gap is a copy operation, but that can be achieved with read+write. All workflows have no dead ends.

Resources