Skip to main content
Glama

pbs_s3_reset_counters

Reset S3 request counters for a specific endpoint, bucket, and optional store prefix. Dry-run returns a plan; confirm=True executes the reset.

Instructions

MUTATION: reset S3 request counters for a matching endpoint/bucket/prefix.

RISK_LOW: resets observability counters, not data — no backup/config content is touched. Dry-run by default (returns a PLAN); confirm=True executes (PUT /admin/s3/{s3-endpoint-id}/reset-counters, synchronous — PBS returns null) and returns {"status": "ok", "result": None}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
s3_idYesS3 client config id whose counters to reset.
bucketYesBucket name for the S3 object store (3-63 chars). REQUIRED.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the reset.
store_prefixNoStore prefix within the bucket (commonly a datastore name) to scope the reset.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Full disclosure: mutation, dry-run default, synchronous execution, return format, safety (no data touched), configuration requirements (PROXIMO_PBS_*). Exceeds expectations given no annotations.

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?

Highly concise, structured with clear labels (MUTATION, RISK_LOW), and front-loaded with purpose. Every sentence adds value without redundancy.

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?

Covers key aspects: purpose, risk, dry-run mechanism, required parameters, execution details, and output format. With output schema present, no further explanation of return values needed.

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 coverage is 100% and parameter descriptions are already detailed. The description adds little beyond mapping terms (endpoint/bucket/prefix) and confirming dry-run behavior, meeting the baseline.

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?

Clearly states the action ('reset S3 request counters'), resource ('counters for matching endpoint/bucket/prefix'), and distinguishes from sibling tools (focus on S3 counters vs. datastore/tape operations).

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 context for dry-run vs. execution and risk level, but does not explicitly compare to alternatives like pbs_s3_check. However, the description is sufficient for basic usage 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