Skip to main content
Glama
EyevinnOSC

Eyevinn Open Source Cloud MCP Server

by EyevinnOSC

osc_list_buckets

Retrieve a list of all buckets from a specified Minio instance on Eyevinn Open Source Cloud Storage.

Instructions

List all buckets on Eyevinn Open Source Cloud Storage (OSC) Minio instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the minio instance

Implementation Reference

  • Handler for osc_list_buckets tool: parses args, gets MinIO instance, calls listBuckets() helper, and returns bucket names as text content.
    case 'osc_list_buckets': {
      const args = ListBucketsSchema.parse(request.params.arguments);
      const instance = await getMinioInstance(context, args.name);
      if (!instance) {
        throw new Error(`Minio instance with name ${args.name} not found`);
      }
      const buckets = await listBuckets(args.name, context);
      return {
        content: [
          {
            type: 'text',
            text: `Buckets on MinIO instance '${args.name}':`
          }
        ].concat(
          buckets.map((bucket) => ({
            type: 'text',
            text: bucket
          }))
        )
      };
  • Helper function that retrieves a MinIO instance and delegates to listMinioBuckets from the minio_minio resource module.
    export async function listBuckets(name: string, context: Context) {
      const instance = await getMinioInstance(context, name);
      if (!instance) {
        throw new Error(`Minio instance with name ${name} not found`);
      }
      return await listMinioBuckets(
        instance.endpoint,
        instance.accessKeyId,
        instance.secretAccessKey
      );
    }
  • Low-level helper that creates a Minio client and calls the minio SDK's listBuckets() to retrieve all bucket names.
    export async function listMinioBuckets(
      endpoint: string,
      accessKeyId: string,
      secretAccessKey: string
    ): Promise<string[]> {
      const minioClient = new Minio.Client({
        endPoint: new URL(endpoint).hostname,
        accessKey: accessKeyId,
        secretKey: secretAccessKey
      });
    
      const buckets = await minioClient.listBuckets();
      return buckets.map((bucket) => bucket.name);
    }
  • Zod schema for osc_list_buckets input: requires a 'name' string matching /^[a-z0-9]+$/ (the MinIO instance name).
    export const ListBucketsSchema = z.object({
      name: z
        .string()
        .regex(/^[a-z0-9]+$/)
        .describe('Name of the minio instance')
    });
    export type ListBucketsSchema = z.infer<typeof ListBucketsSchema>;
  • src/tools/osc.ts:39-44 (registration)
    Registration of osc_list_buckets tool in the listOscTools() function, which is called from index.ts to register with MCP server.
    {
      name: 'osc_list_buckets',
      description:
        'List all buckets on Eyevinn Open Source Cloud Storage (OSC) Minio instance',
      inputSchema: zodToJsonSchema(ListBucketsSchema)
    }
Behavior2/5

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

No annotations are provided, and the description gives no behavioral details beyond listing. It does not mention permissions, pagination, error handling, or any side effects.

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?

Single sentence of 15 words, front-loaded with the verb and object. No wasted words, efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list operation with one required parameter and no output schema, the description is adequate but lacks information about the return format or any additional context 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?

The description does not add meaning beyond the input schema, which already describes the 'name' parameter with a pattern. With 100% schema coverage, the baseline of 3 is appropriate.

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?

The description clearly states the action (List), resource (buckets), and context (Eyevinn Open Source Cloud Storage Minio instance). It distinguishes from sibling tools like osc_create_bucket and osc_list_files.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. There is no mention of prerequisites or exclusions, leaving the agent to infer usage from the tool name alone.

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/EyevinnOSC/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server