Skip to main content
Glama

shiply

by now.shiply
OverviewDiscussionsAdmin

Write a drive file

drive_put_file
Idempotent

Write a file into a Drive (driveId = drv_… or "default"). content is utf8 or base64. Use for agent memory, notes, context, assets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesdestination path inside the drive, e.g. notes/context.md
contentYesfile contents (utf8 text, or base64 when encoding=base64)
driveIdYesdrive id (drv_…) or "default"
encodingNodefault utf8; base64 for binary

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / content / description
      Added value: +"file contents (utf8 text, or base64 when encoding=base64)"
    • addedInput schema / properties / driveId / description
      Added value: +"drive id (drv_…) or \"default\""
    • addedInput schema / properties / encoding / description
      Added value: +"default utf8; base64 for binary"
    • addedInput schema / properties / path / description
      Added value: +"destination path inside the drive, e.g. notes/context.md"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {}
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, indicating safe repeated calls. The description adds encoding details (utf8/base64) and drive ID format but does not specify whether the tool overwrites existing files or creates new ones. This missing information is relevant for understanding 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?

The description is two sentences, front-loading the purpose and key constraints. Every word is relevant, with no redundancy or fluff.

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 that an output schema exists and annotations provide safety context, the description covers core purpose and use cases. However, it omits overwrite behavior, which is a minor gap for a write tool with idempotent hint. Still, it is largely complete for its complexity.

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?

The input schema has 100% parameter description coverage, so the schema already explains each parameter. The description reiterates content encoding but adds no meaningful new semantic information beyond what is in the schema.

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 a file into a Drive, specifies the driveId format, and lists use cases like memory, notes, context, and assets. This distinguishes it well from siblings like drive_list_files and drive_delete_file.

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?

It provides explicit use cases (agent memory, notes, context, assets) but does not offer when-not-to-use guidance or name alternative tools for similar tasks. The context is clear but lacks exclusions.

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

All shiply 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.

Resources