Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

s3_upload_object

Upload a local file to an S3 bucket using provider, bucket, key, and local_path; overwrites the destination object if it already exists.

Instructions

Upload a local file to an S3 bucket. local_path must resolve under home, cwd, or ~/Downloads. Overwrites the destination key if it exists. Reserved for dangerous guard mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesDestination object key.
bucketYesDestination bucket name.
regionNoRegion the bucket lives in (e.g. 'eu-central-1'). Omit unless you know it — it is resolved automatically. AWS, and OVH when no endpoint URL is configured (pass the region s3_list_buckets reports). Rejected for Hetzner, and for an OVH endpoint URL set by hand, whose region is fixed by that endpoint.
accountNoAccount label of the provider whose object storage to use; omit for that provider's default account.
providerYesStorage provider.
local_pathYesLocal file path to upload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.28.0
    • addedInput schema / properties / account
      Added value: +{
+  "description": "Account label of the provider whose object storage to use; omit for that provider's default account.",
+  "type": "string"
+}
    • changedInput schema / properties / region / description
      Previous value: -"Region the bucket lives in (e.g. 'eu-central-1'). Omit unless you know it — it is resolved automatically. AWS only; rejected for Hetzner/OVH, whose region is fixed by the configured endpoint URL."New value: +"Region the bucket lives in (e.g. 'eu-central-1'). Omit unless you know it — it is resolved automatically. AWS, and OVH when no endpoint URL is configured (pass the region s3_list_buckets reports). Rejected for Hetzner, and for an OVH endpoint URL set by hand, whose region is fixed by that endpoint."
  2. Changed1 schema field changedv2.24.2
    • addedInput schema / properties / region
      Added value: +{
+  "description": "Region the bucket lives in (e.g. 'eu-central-1'). Omit unless you know it — it is resolved automatically. AWS only; rejected for Hetzner/OVH, whose region is fixed by the configured endpoint URL.",
+  "type": "string"
+}
  3. Addedv2.24.0
  4. Removedv2.23.8
  5. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the destination key is overwritten (a destructive behavior) and that local_path must resolve under home, cwd, or ~/Downloads, but it omits permissions required, error behavior, and whether it creates missing buckets.

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 tightly written sentences with the core action front-loaded and no redundant or filler content. The path restriction and overwrite disclosure follow naturally and earn their place.

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?

For a simple upload tool with no output schema and no annotations, the description covers the main behavioral and safety-relevant facts. It could be more complete regarding authorization requirements and failure modes, but it is sufficient for correct invocation.

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 coverage is 100%, so the baseline is 3, but the description adds meaningful constraints for local_path (must resolve under home, cwd, or ~/Downloads) and key (overwrite behavior) that are not present in the schema descriptions, justifying a higher score.

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 states a specific verb and resource: 'Upload a local file to an S3 bucket.' This clearly distinguishes it from download/copy/move siblings by name, but it never explicitly contrasts with them, so the agent must infer the distinction.

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 phrase 'Reserved for dangerous guard mode' gives a condition for use, but it does not explain when to choose this over s3_copy_object or other alternatives, nor does it state when the tool is unavailable. Usage context is only implied.

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