Skip to main content
Glama

validate_s3

Test read and write access to an S3 bucket using provided credentials and region. Ensures S3 export jobs will succeed by verifying bucket permissions before submission.

Instructions

Validate S3 credentials by testing read/write access to the specified bucket. Use before submitting a job with S3 export.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
s3_bucketYesS3 bucket name
s3_access_key_idYesAWS access key ID
s3_secret_access_keyYesAWS secret access key
s3_regionYesAWS region (e.g. us-east-1)

Implementation Reference

  • src/mcp.ts:259-273 (registration)
    MCP tool registration for 'validate_s3' with name, description, and JSON inputSchema defining required params: s3_bucket, s3_access_key_id, s3_secret_access_key, s3_region.
    {
      name: "validate_s3",
      description:
        "Validate S3 credentials by testing read/write access to the specified bucket. Use before submitting a job with S3 export.",
      inputSchema: {
        type: "object" as const,
        properties: {
          s3_bucket: { type: "string", description: "S3 bucket name" },
          s3_access_key_id: { type: "string", description: "AWS access key ID" },
          s3_secret_access_key: { type: "string", description: "AWS secret access key" },
          s3_region: { type: "string", description: "AWS region (e.g. us-east-1)" },
        },
        required: ["s3_bucket", "s3_access_key_id", "s3_secret_access_key", "s3_region"],
      },
    },
  • Handler case that extracts args from the MCP request and calls getClient().validateS3() with the provided S3 parameters.
    case "validate_s3":
      result = await getClient().validateS3({
        s3_bucket: args!.s3_bucket as string,
        s3_access_key_id: args!.s3_access_key_id as string,
        s3_secret_access_key: args!.s3_secret_access_key as string,
        s3_region: args!.s3_region as string,
      });
      break;
  • Client-side helper method that sends a POST request to /api/v1/jobs/validate_s3 with the S3 credential params object.
    async validateS3(params: {
      s3_bucket: string;
      s3_access_key_id: string;
      s3_secret_access_key: string;
      s3_region: string;
    }): Promise<any> {
      return this.request("POST", "/api/v1/jobs/validate_s3", params);
    }
  • CLI command handler for 'validate-s3' that collects S3 options from command line, calls client.validateS3(), and outputs results.
    .command("validate-s3")
    .description("Validate S3 credentials before submitting a job")
    .requiredOption("--s3-bucket <bucket>", "S3 bucket name")
    .requiredOption("--s3-key <key>", "AWS access key ID")
    .requiredOption("--s3-secret <secret>", "AWS secret access key")
    .requiredOption("--s3-region <region>", "AWS region")
    .option("--json", "Output as JSON")
    .action(async (opts) => {
      try {
        const client = getClient();
        const result = await client.validateS3({
          s3_bucket: opts.s3Bucket,
          s3_access_key_id: opts.s3Key,
          s3_secret_access_key: opts.s3Secret,
          s3_region: opts.s3Region,
        });
    
        if (opts.json) {
          output.json(result);
          return;
        }
    
        console.log("S3 credentials validated successfully.");
      } catch (err: any) {
        console.error(`S3 validation failed: ${err.message}`);
        process.exit(1);
      }
    });
  • Input schema for validate_s3 tool: object type with string properties s3_bucket, s3_access_key_id, s3_secret_access_key, s3_region, all required.
    inputSchema: {
      type: "object" as const,
      properties: {
        s3_bucket: { type: "string", description: "S3 bucket name" },
        s3_access_key_id: { type: "string", description: "AWS access key ID" },
        s3_secret_access_key: { type: "string", description: "AWS secret access key" },
        s3_region: { type: "string", description: "AWS region (e.g. us-east-1)" },
      },
      required: ["s3_bucket", "s3_access_key_id", "s3_secret_access_key", "s3_region"],
    },
Behavior3/5

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

No annotations provided, so description is sole source. It mentions testing read/write access, but does not disclose potential side effects like creating temporary test objects or the exact nature of the validation. Adequate but incomplete.

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 concise sentences. First sentence describes action, second provides usage context. No wasted words.

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?

No output schema, so description should include return value hints. It does not mention what the tool returns on success/failure. Adequate for purpose and usage but missing behavioral details.

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 covers all parameters with descriptions (100% coverage). The description adds no new information beyond schema. Baseline 3 applies.

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?

Description clearly states the verb 'validate', resource 'S3 credentials', and context 'bucket'. It distinguishes from sibling tools which deal with jobs, evaluations, models, etc., as it's a validation tool.

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?

Explicitly states 'Use before submitting a job with S3 export', giving clear context. No explicit exclusions or alternatives, but the usage is straightforward for a validation tool.

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/cerebrixos-org/tuning-engines-cli'

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