Skip to main content
Glama

NS Pros MCP Gateway

aws-mcp__aws___get_presigned_url

Generate pre-signed S3 URLs for uploading or downloading files. Use BEFORE run_script when an operation requires a local file. Use for direct S3 uploads/downloads. Max upload 5 GB; larger files use multipart. For uploads: generates PUT URL. For downloads: generates GET URL. No special headers needed unless s3_params provided—then corresponding HTTP headers MUST be included or request fails with SignatureDoesNotMatch.

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": {
      "requests": "<requests>"
    },
    "name": "aws-mcp__aws___get_presigned_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestsYesArray of 1-25 presigned URL requests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does well: it explains PUT-vs-GET mapping, the 5 GB ceiling, and the critical failure mode (SignatureDoesNotMatch) when s3_params are used without matching headers. It stops short of stating auth/permission requirements or that the tool only mints a URL without transferring data, and it omits that requests are batched (1-25 per call).

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 purpose, then guidance, then constraints and failure modes—good ordering with no filler. There is mild redundancy between 'Use BEFORE run_script...' and 'Use for direct S3 uploads/downloads,' which say nearly the same thing.

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 single-object parameter tool with no annotations and no output schema, the description covers the behaviors an agent needs to invoke it correctly: verb selection, size limit, and header requirements. The main omission is that it never states the return value is a set of URLs (no output schema exists to cover this), nor that multiple requests can be bundled in one call.

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 above baseline by tying the 'operation' value to the actual HTTP verb and spelling out the operational consequence of s3_params (headers MUST be included or the request fails with SignatureDoesNotMatch). The expires_in cap is left entirely to the schema, which already documents it fully.

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?

Opens with a specific verb and resource: 'Generate pre-signed S3 URLs for uploading or downloading files,' which immediately distinguishes it from the execution-oriented sibling run_script. The upload/download duality is stated up front rather than buried.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use BEFORE run_script when an operation requires a local file,' naming the alternative and the condition that selects it. It also bounds usage with 'Max upload 5 GB; larger files use multipart,' giving a concrete when-not-to-use case.

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.