Loading ToolBench
High-performance MCP server and library providing a cloud-native replacement for mcp-server-filesystem. Supports S3, Azure Blob, GCS, and SQLite with VFS cache coherence.
Cloud FS provides 18 tools with consistent naming (verb_noun pattern) and basic descriptions. All tools have input schemas with type definitions. However, descriptions are often terse (10-50 chars), parameter descriptions lack detail on constraints/formats, and output schemas are not documented. Error handling guidance is minimal. The shell tool is notably complex but under-documented. No tool annotations (readOnlyHint/destructiveHint) despite clear risk levels. Composition is reasonable, tools are single-purpose, but chaining metadata is sparse.
Copy a file in cloud storage
Create a directory in cloud storage
Delete a file from cloud storage
Get metadata information about a file
Get detailed metadata for a file including tags and custom attributes
Generate a presigned URL for temporary access to a file
Search for text content in files
List files and directories in a cloud storage path
Descriptions are terse (10-60 chars) and lack context on WHEN to use each tool. Example: 'Read file content from cloud storage' does not explain when to call this vs grep_files or get_file_info.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels declared (READ_ONLY, WRITE, DESTRUCTIVE). This prevents clients from applying safety guards or warning users before destructive operations.
Parameter descriptions lack constraint details. 'path' is described as 'Cloud storage path (e.g., s3://bucket/key)' but does not specify: required format, max length, allowed characters, or what happens if path is invalid.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | <=2025-11-25 | v2 |
List version history of a file
Move or rename a file in cloud storage
Apply a unified diff patch to a file
Read file content from cloud storage
Restore a file to a previous version
Search for files matching a pattern in cloud storage
Set metadata tags and custom attributes on a file
Execute POSIX-like shell commands against the cloud filesystem. Supports pipes (|), input redirection (<), output redirection (>, >>), and command list operators (&& for AND-chaining, || for OR-fallback, ; for sequencing). All paths must be cloud URIs (e.g. s3://bucket/key). No real shell is spawned — commands run in-process against the VFS. Supported commands: ls, cat, head, tail, cp, mv, rm, mkdir, touch, stat, find, grep, wc, du, echo, tee, diff. Destructive commands (rm, mv) require --enable-delete.
Opens an interactive terminal UI for executing cloud-fs shell commands. Supports ls, cat, grep, find, and 13 more POSIX-like commands with piping (|) and redirection (>, >>).
Write file content to cloud storage
Output schemas are not documented. Tools return results but LLMs cannot see what fields to expect (e.g., does list_directory return 'files' or 'items'? Does it include 'size', 'modified_time'?).
shell and shell_app tools are under-documented. shell description (long) mentions 13+ commands and piping but does not explain error handling, timeout behavior, or what happens if a command fails mid-pipeline. shell_app lacks clarity on interactive vs batch modes.