Skip to main content
Glama
hostkey-cloud

hostkey-mcp-server

Official
by hostkey-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

s3_get_buckets

Read-only

Lists S3 account buckets and usage using an S3 UID or account ID from s3_get_users; track any returned task key with check_task.

Instructions

List S3 account buckets and usage (s3/get_buckets_rmq). Pass s3uid or account_id from s3_get_users. May return a task key — then track with check_task.

Input Schema

NameRequiredDescriptionDefault
s3uidNoS3 account UID from s3_get_users.s3uid
account_idNoNumeric id from s3_get_users.id (alias; resolved to s3uid)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.8
    • changedInput schema / properties / account_id / description
      Previous value: -"Deprecated alias for s3uid; prefer s3uid"New value: +"Numeric id from s3_get_users.id (alias; resolved to s3uid)"
    • changedInput schema / properties / s3uid / description
      Previous value: -"S3 account UID (s3uid) from s3_get_users or create_account/order. Numeric id (e.g. 13457) or string uid."New value: +"S3 account UID from s3_get_users.s3uid"
    • removedInput schema / required
      Removed value: -[
-  "s3uid"
-]
  2. Changed3 schema fields changedv1.0.4
    • changedInput schema / properties / account_id / description
      Previous value: -"S3 account ID (if required; check via s3_get_users)"New value: +"Deprecated alias for s3uid; prefer s3uid"
    • addedInput schema / properties / s3uid
      Added value: +{
+  "description": "S3 account UID (s3uid) from s3_get_users or create_account/order. Numeric id (e.g. 13457) or string uid.",
+  "type": [
+    "string",
+    "number"
+  ]
+}
    • addedInput schema / required
      Added value: +[
+  "s3uid"
+]
  3. Changed1 schema field changedv1.0.3
    • changedInput schema / properties / account_id / description
      Previous value: -"ID S3-аккаунта (если требуется; уточняйте через s3_get_users)"New value: +"S3 account ID (if required; check via s3_get_users)"
  4. First observedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark this as read-only and open-world. The description adds useful behavioral context beyond annotations: it may return a task key and that task should be tracked with check_task, revealing an async workflow. It does not discuss permissions or return shape, but that is less critical for a read-only list tool.

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?

The description is two compact clauses, front-loads the core action, and every sentence provides actionable information: the resource, the ID source, and the task-tracking follow-up.

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 read-only list tool with complete schema coverage and annotations, the description covers the key prerequisites and the async-task follow-up. It does not explain what 'usage' contains or whether calling with no ID lists everything, but those gaps are minor.

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%, so both parameters are already documented, including their provenance and the account_id alias behavior. The description repeats the provenance from s3_get_users but adds no syntax or constraint details beyond the schema.

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: 'List S3 account buckets and usage.' The endpoint hint '(s3/get_buckets_rmq)' implicitly distinguishes it from the queue-based sibling, but no explicit sibling differentiation is given.

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?

It tells the agent where to get the required identifiers ('Pass s3uid or account_id from s3_get_users') and what to do if a task key is returned ('track with check_task'). It does not explicitly compare with the sibling s3_get_buckets_via_queue.

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