Skip to main content
Glama

NS Pros MCP Gateway

aws-mcp__aws___run_script

Execute Python code in sandboxed environment with AWS API access via call_boto3. No network except call_boto3.

async def call_boto3(
    *,
    service_name: str,
    operation_name: str,
    region_name: str | None = None,
    params: dict | None = None,
) -> dict: ...  # the AWS response itself

operation_name MUST be the PascalCase AWS API operation name (e.g. ListBuckets, GetTable). Do not use the snake_case boto3 method name (list_buckets, get_table);

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": {
      "code": "<code>"
    },
    "name": "aws-mcp__aws___run_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesPython code to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the load and it does disclose real traits: sandboxed execution and a network block with a single escape hatch through call_boto3. It omits what an agent most needs to know about a code-execution tool, namely whether state persists between calls, what timeouts or resource limits exist, whether mutating AWS operations are permitted, and how the final result is surfaced.

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

Conciseness4/5

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

Front-loaded with the core statement, then a compact signature block and a necessary naming constraint. The embedded code block earns its space because the helper's signature is otherwise undiscoverable, though the trailing dangling semicolon and abrupt ending read as unfinished.

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 one-parameter code-execution tool with no annotations and no output schema, the description should explain what the tool returns (stdout, last expression, or call_boto3's dict) and whether sandbox state survives across invocations. It documents the AWS helper thoroughly but leaves the overall execution contract underspecified.

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 bare 'Python code to execute' would only merit a 3. The embedded call_boto3 signature and the return type annotation ('the AWS response itself') add genuine meaning about what the code string may legitimately contain, which goes beyond the schema.

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?

States a specific verb and resource: execute Python code in a sandboxed environment, with AWS API access mediated by call_boto3. That is clearly distinguishable from the documentation-reading and regional-listing siblings, which cannot run arbitrary code.

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?

The description implies when this tool is useful (you need Python plus AWS API calls) and gives one hard constraint: no network except call_boto3. It never states when not to use it or which sibling to prefer for documentation, region listing, or presigned URLs, so the agent must infer the routing itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.