s3-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-s3-bucketsC | List all S3 buckets in your AWS account |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility for ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate. The tool name 'list-s3-buckets' follows a clear verb_noun pattern.
A single tool for an S3 server is too few for the apparent scope, as S3 involves operations like uploading, downloading, deleting objects, and managing buckets beyond listing. This minimal set will likely cause agent failures due to significant functional gaps.
The tool surface is severely incomplete for an S3 domain, covering only bucket listing. There are obvious gaps for core operations such as creating/deleting buckets, managing objects (upload, get, delete), and other essential S3 functionalities, making it inadequate for typical use cases.