STRG.com s3-compatible object storage for people and agents

This session's access key

session_info

Read-onlyIdempotent

Returns the access key this session is connected with: its id and secret access key, every permission, the buckets and key prefix it is limited to, each region's S3 endpoint, and ready-to-paste setup for environment variables, the AWS CLI / SDK profiles and rclone. Use it to configure an S3 tool for bulk or long-running work. For a key whose irreversible operations the user confirms, the secret is withheld.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "session_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`via`	Yes	bearer: the client sends the key itself; oauth: a key created when connecting
`label`	Yes
`notes`	Yes
`setup`	Yes
`confirms`	Yes	true: the user confirms each operation that cannot be undone, and the secret is withheld - use execute_s3_operation and create_presigned_url
`endpoints`	Yes	The S3 endpoint of each region - a bucket answers on its own region's only
`keyPrefix`	Yes	Object keys must start with this; null is any key
`accessKeyId`	Yes
`bucketScope`	Yes	null is every bucket, including ones created later
`permissions`	Yes	Everything the key may do, the always-included permissions too
`secretAccessKey`	Yes	The connected key's secret - never share or commit it. Empty when confirms is true

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: it discloses a security condition (the secret is withheld when the key's irreversible operations are user-confirmed). That conditional redaction is exactly the kind of trait an agent must know before planning to use the returned credentials. The phrasing of that condition is somewhat compressed, which keeps it from a 5.

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 payload, then purpose, then the caveat — a sensible order with no filler sentences. The middle clause is a long comma-separated list, which is dense but every item is a distinct return field the agent would otherwise have to discover.

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?

An output schema exists, so return-value detail is optional; the description nevertheless outlines the shape, which helps an agent decide whether to call it. What remains slightly under-specified is the exact condition under which the secret is withheld — "a key whose irreversible operations the user confirms" is terse and could matter for planning.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. No misleading parameter discussion is present.

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 concrete verb and resource — returns this session's access key — and enumerates the payload (id, secret, permissions, bucket/prefix limits, per-region S3 endpoints, ready-to-paste env/CLI/rclone setup). That enumeration distinguishes it from list_access_keys (which lists other keys) and from create_access_key, so an agent can route correctly without opening a schema.

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?

"Use it to configure an S3 tool for bulk or long-running work" gives a clear, actionable trigger, which implicitly routes short one-off operations to execute_s3_operation. No explicit exclusions or named alternatives are given, so it stops short of full when/when-not coverage.

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

All STRG.com s3-compatible object storage for people and agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?