Skip to main content
Glama

pbs_s3_client_create

Create a persistent PBS S3 client configuration for object storage access. Dry-run generates a plan; confirm=True executes the API call.

Instructions

MUTATION: create a PBS S3 client configuration.

RISK_MEDIUM: creates a PERSISTENT CREDENTIAL-BEARING entry (mirrors pbs_remote_create, not the LOW-rated additive-config pattern of e.g. pbs_tape_pool_create). SECRET CONTRACT: secret-key is NEVER written to the audit ledger or the dry-run PLAN — it is forwarded RAW only to the real PBS API on confirm=True (the create must actually work). access-key is NOT redacted (schema-confirmed non-secret). Dry-run by default (returns a PLAN); confirm=True executes (POST /config/s3, synchronous — PBS returns null) and returns {"status": "ok", "result": None}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNoPort to access the S3 object store (1-65535).
s3_idYesNew S3 client config id (3-32 chars, alnum/underscore start, then alnum/./_/-).
regionNoRegion to access the S3 object store (lowercase alnum/underscore/hyphen, <=32 chars).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation.
rate_inNoInbound rate limit as a byte size with unit, e.g. '10MB' (1-64 chars).
burst_inNoInbound burst limit as a byte size with unit (1-64 chars).
endpointYesEndpoint hostname/IPv4/IPv6 to access the S3 object store (may use {{bucket}}./{{region}} templating).
rate_outNoOutbound rate limit as a byte size with unit (1-64 chars).
burst_outNoOutbound burst limit as a byte size with unit (1-64 chars).
access_keyYesAccess key for the S3 object store. NOT treated as secret — PBS itself returns this unredacted on every read (AWS convention: identifies the credential pair, is not itself the credential).
path_styleNoUse path-style bucket addressing instead of vhost-style.
secret_keyYesSecret key for the S3 object store. SECRET — never written to the audit ledger or the dry-run PLAN.
fingerprintNoX509 certificate fingerprint (sha256, 32 colon-separated hex byte-pairs) to pin the endpoint's TLS cert.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.
provider_quirksNoProvider-specific implementation quirks: 'skip-if-none-match-header' and/or 'delete-objects-via-delete-object'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, but the description fully discloses: it's a MUTATION creating a persistent credential-bearing entry, the secret contract (secret_key never written to audit/plan, access_key not redacted), dry-run by default, and the need for PROXIMO_PBS_* config. Rich behavioral context.

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?

Every sentence earns its place. Front-loaded with purpose and risk. No fluff, despite covering necessary complexity. Information density is high without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 15 parameters, 4 required, no annotations, and an existing output schema, the description covers the core behavior, risk, security implications, dry-run pattern, and return format. Nothing essential is missing.

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 baseline is 3. The description adds value by highlighting which parameters are sensitive (secret_key) and the overall credential-bearing nature, beyond the schema's detailed descriptions.

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?

Description starts with 'MUTATION: create a PBS S3 client configuration', clearly stating the verb and resource. It further distinguishes from sibling tools by comparing to pbs_remote_create and pbs_tape_pool_create, making the purpose highly specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly explains when to use this tool vs alternatives (mirrors pbs_remote_create, not the additive-config pattern). Also describes dry-run default and confirm=True behavior, plus the RISK_MEDIUM classification, providing complete scenario guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server