Skip to main content
Glama
Sign In
Aktar

Aktar

Official
by getaktar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Browse a bucket

list_bucket
Read-only

Lists folders and files directly under a destination bucket folder, including items not uploaded through Aktar, and returns a continuation token for paginated results.

Instructions

List the folders and files right under a folder of a destination's bucket, including files not uploaded with Aktar. Returns nextContinuationToken when there's more.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixNoFolder to list, like "docs/2026/". Leave out for the top.
destinationNoDestination name or ID. Leave out for the selected one.
continuationTokenNonextContinuationToken from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds genuinely new behavior: listing is limited to one level ('right under a folder'), includes files outside Aktar's own uploads, and paginates via nextContinuationToken. It still omits ordering, result size, and whether folder entries are returned as items, but the added context is solid.

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?

Two short sentences, both load-bearing: the first defines scope and contents, the second covers pagination. Nothing is repeated from the title or schema.

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 browse tool with a fully documented 3-parameter schema and no output schema, the description covers the essentials: scope, contents, and pagination. It would be complete at 5 if it stated ordering or roughly what each returned entry contains.

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 the baseline is 3; the description earns extra by explaining that prefix scopes to a single folder level and that continuationToken comes from the previous page's nextContinuationToken. That ties the parameter to the returned value rather than restating 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 gives a specific verb and resource (list folders and files in a destination's bucket) and clarifies the scope with 'right under a folder', which signals a non-recursive listing. It partially differentiates itself from siblings via 'including files not uploaded with Aktar', but never names an alternative tool outright.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer this is for browsing one folder level, and the note about non-Aktar files hints that search_uploads is a different path. There is no explicit when-to-use/when-not statement or named alternative, so an agent must infer the boundary itself.

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