Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

s3_move_object

Move an S3 object between buckets or keys by copying server-side and deleting the source; overwrites the destination and cannot be undone.

Instructions

Move an S3 object (server-side copy then delete source). Irreversible on the source. 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.
src_regionNoRegion the SOURCE bucket lives in. Only needed when the source and destination are in different regions.

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. Changed2 schema fields 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"
+}
    • addedInput schema / properties / src_region
      Added value: +{
+  "description": "Region the SOURCE bucket lives in. Only needed when the source and destination are in different regions.",
+  "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 well: it discloses irreversibility on the source, that the destination is overwritten, the underlying copy-then-delete sequence, and the guard-mode requirement. It stops short of describing partial-failure behavior (copy succeeds but delete fails) or required permissions, but the safety-critical traits are all present.

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, each earning its place, with the core action front-loaded and the two risk traits (irreversible source, destination overwrite) following immediately. No filler.

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 mutation tool with no annotations and no output schema, the description covers the essential behavioral facts (destructive source effect, destination overwrite, guard-mode gating). It is only slightly short on edge-case and failure semantics, which is a minor gap for this complexity level.

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 8 parameters including the region quirks and account resolution. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource ('Move an S3 object') and immediately explains the mechanism (server-side copy then delete source), which cleanly distinguishes it from the s3_copy_object and s3_delete_object siblings. An agent can tell exactly what this does without opening the schema.

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?

'Reserved for dangerous guard mode' gives a genuine usage constraint, and the copy-then-delete phrasing implies the copy+delete alternative. However, it never explicitly names when to prefer s3_copy_object or s3_delete_object over this combined operation, leaving the routing decision to inference.

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