Skip to main content
Glama
Sign In
Code Gym AWS Emulator MCP

Code Gym AWS Emulator MCP

by B11-Health
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

s3_get_object

Read-onlyIdempotent

Read UTF-8 text content from a file in an emulated S3 bucket. Use it to inspect stored objects during local AWS testing without an account.

Instructions

Read UTF-8 text from emulated S3

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bucket": "<bucket>",
      "key": "<key>"
    },
    "name": "s3_get_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
bucketYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0-beta.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: content is decoded as UTF-8 text, implying failure or mojibake for binary payloads. It says nothing about missing-key behavior or error signaling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is efficient. However, the terseness tips into under-specification rather than disciplined concision, so the brevity does not fully earn its place.

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

Completeness2/5

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

For a read tool with no output schema, the description should indicate what comes back (the object body as a string) and what happens when the key is absent. Neither is covered, and the two required parameters are left unexplained, leaving notable gaps for a simple but foundational operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so both required parameters (bucket, key) are undocumented in the schema. The description does not compensate at all — it never explains what a bucket or key is, nor any format constraints, so the agent gets no meaning beyond the property names.

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?

States a specific verb and resource ('Read ... from emulated S3') plus a meaningful constraint ('UTF-8 text'), which separates it from s3_put_object and s3_delete_object. It stops short of naming the bucket/key addressing model, but the action is unambiguous.

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?

There is no when-to-use guidance, no mention of alternatives, and no exclusions. The agent must infer from the name that this is the read path for object contents and that binary objects are out of scope.

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