Opsphere — DevOps & SRE Intelligence

AWS SSO Login

aws_sso_login

Start/renew the SSO session for a profile (without restarting the server).

Input Schema

Name	Required	Description	Default
`profile`	Yes	AWS profile name (e.g. your-tenant-pre)
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026
- addedOutput schema / properties / data / properties / errorCode
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / retryable
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / data / properties / status
```
Added value: +{
+  "type": "string"
+}
```
Changed18 schema fields changedOct 26, 2026
- addedOutput schema / properties / data / properties / deviceCode
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / expiresIn
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / data / properties / flowType
```
Added value: +{
+  "enum": [
+    "completed",
+    "device_code",
+    "oauth_pkce",
+    "unknown"
+  ],
+  "type": "string"
+}
```
- removedOutput schema / properties / data / properties / format
```
Removed value: -{
-  "enum": [
-    "plain",
-    "markdown",
-    "json"
-  ],
-  "type": "string"
-}
```
- addedOutput schema / properties / data / properties / instructions
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / oauthUrl
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / profile
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / ssoRequired
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / data / properties / success
```
Added value: +{
+  "type": "boolean"
+}
```
- removedOutput schema / properties / data / properties / text
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / data / properties / userCode
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / verificationUri
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / verificationUriComplete
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / workaround
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / data / required
```
Previous value: -[
-  "text"
-]New value: +[
+  "flowType",
+  "profile"
+]
```
- addedOutput schema / properties / dataSchemaVersion
```
Added value: +{
+  "const": 2,
+  "type": "number"
+}
```
- changedOutput schema / required
```
Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]
```
First observedOct 15, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by clarifying that it starts or renews a session without restarting the server, but it omits auth-flow details, expiry behavior, and side effects of renewing a session.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no wasted words. It states the action and a key constraint immediately, making it easy to scan.

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?

An output schema exists, so return values need not be explained. However, given the crowded family of AWS SSO login tools, the description is too thin to fully help an agent choose this variant or understand the session renewal lifecycle; it is minimally adequate but incomplete for the tool's context.

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

Parameters3/5

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

Schema description coverage is 100%, so both the required 'profile' and optional 'context_id' parameters are fully documented in the schema. The description only echoes 'for a profile' and adds no syntax or selection guidance beyond what the schema provides; baseline 3 is appropriate.

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?

The description gives a specific verb+resource ('Start/renew the SSO session') and clarifies it works for a profile without restarting the server. It does not distinguish this tool from sibling login tools such as aws_sso_login_device_start, aws_sso_login_remote, or aws_sso_login_global_start, leaving ambiguity about which login entry point to select.

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 explicit guidance on when to use this tool versus the many sibling login variants. The parenthetical 'without restarting the server' implies renewal, but no exclusions, prerequisites, or alternatives are named, so the agent must infer usage from tool names.

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

All Opsphere — DevOps & SRE Intelligence 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?