Browse S3-compatible storage by listing objects under a bucket and prefix, with delimiter-based virtual folders and cursor pagination for large result sets.
模拟分层虚拟目录树（Delimiter 默认为 /），支持游标分页
| Name | Required | Description | Default |
|---|---|---|---|
| bucket | No | ||
| prefix | No | ||
| max_keys | No | ||
| delimiter | No | ||
| continuation_token | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the delimiter defaults to '/' and that cursor pagination is supported, but omits critical behavioral details like read-only nature, permission requirements, return format, sorting, and the effect of max_keys.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with no wasted words, and the delimiter default is front-loaded. It is appropriately sized for its content, though the content itself is sparse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 5 parameters, no annotations, no output schema, and 0% schema description coverage, the description is significantly incomplete. It does not explain key parameters like bucket and prefix, nor does it describe what the operation returns.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for all 5 parameters. The description only clarifies the delimiter default ('/') and implies continuation_token via 'cursor pagination', leaving bucket, prefix, and max_keys undocumented in both schema and description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description says it simulates a hierarchical virtual directory tree and supports cursor pagination, which hints at listing objects, but it never explicitly states the verb 'list' or the resource 'objects'. It relies on the tool name to convey the core action and does not distinguish itself from siblings like search_objects.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as search_objects or list_buckets. No prerequisites, conditions, or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.