createS3SessionGenerate expiring S3 credentials to access Cloady volumes. Specify workspace slug and read or write access; write requires developer role.
The credentials are derived and expire on their own; access: "write" needs the developer role. Buckets are named <instance id without dashes>-<volume>.
| Name | Required | Description | Default |
|---|---|---|---|
| requestBody | No | The JSON request body. | |
| workspaceSlug | Yes |
Changes observed during successful MCP inspections.
v0.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description mentions that credentials are derived and expire, and the bucket naming convention, but does not disclose the full behavior (e.g., that it returns temporary credentials, creates a session, or has side effects). The destructiveHint annotation is not addressed at all, so the description fails to clarify the operation's safety profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, which is concise, but it is dense and cryptic. It packs multiple technical details without clear separation or prioritization, making it less readable than ideal.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description provides some contextual details about credentials and buckets, but it does not give enough information for an agent to understand what the tool actually does, what it returns, or when to use it. It relies heavily on the tool name for context, which is insufficient for complete understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description explains the 'access' parameter by noting that 'write' access requires the developer role, which adds meaning. However, it does not explain 'workspaceSlug' or how the bucket naming relates to the parameters, leaving some parameters under-specified.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description lacks an explicit verb like 'creates' or 'generates', instead stating technical facts about credential expiry and bucket naming. The tool name and title imply the purpose, but the description itself does not clearly state that it creates an S3 session.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives (e.g., endS3Session). The description does not mention prerequisites, typical scenarios, or distinguish this from related operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.