Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

s3_copy_object

Copy an S3 object server-side between buckets or keys on AWS, Hetzner, or OVH, overwriting the destination if it already exists.

Instructions

Server-side copy of an S3 object within the same provider. Overwrites the destination if it exists. Reserved for dangerous guard mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoRegion the DESTINATION 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.
dst_keyYesDestination object key.
src_keyYesSource object key.
providerYesStorage provider.
dst_bucketYesDestination bucket name.
src_bucketYesSource bucket name.

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 DESTINATION 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 DESTINATION 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 DESTINATION 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

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose important behavior: it is a server-side copy (no data transfer), it overwrites the destination if it exists, and it is restricted to dangerous guard mode. It does not mention source preservation explicitly, permission requirements beyond guard mode, or error handling.

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, front-loaded sentences that each add distinct value: purpose/scope, destructive behavior, and usage restriction. No filler or redundancy.

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 7-parameter tool with no output schema and no annotations, the description covers the essential purpose, overwrite behavior, and guard-mode restriction. It omits return-value details and source-preservation confirmation, but these are minor for a straightforward copy operation.

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 all seven parameters in detail. The description adds no parameter-level information beyond what the schema provides, so the baseline of 3 is appropriate.

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?

States a specific verb and resource ('Server-side copy of an S3 object') and scopes it to the same provider, so the agent knows it is not a cross-provider operation. However, it does not explicitly distinguish itself from siblings like s3_move_object or s3_upload_object, leaving the agent to infer the difference from the verb alone.

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?

Provides a clear usage context: 'Reserved for dangerous guard mode,' which tells the agent this is not a normal-path operation. It does not name alternatives (e.g., s3_move_object) or give explicit when-not conditions beyond the guard-mode restriction.

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