Opsphere — DevOps & SRE Intelligence

AWS SSO Device Code Start

aws_sso_login_device_start

Module: aws (not aws-sessions). Start the Device Code flow for SSO (URL + code) and return deviceCode for polling. If a valid session already exists, returns status "already_authenticated" without starting a new login.

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

A4/5.0

Behavior4/5

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

Annotations already indicate the tool is not read-only and not destructive. The description adds valuable behavioral context: it returns a deviceCode for polling and conditionally returns 'already_authenticated' if a session exists, without starting a new login. It does not cover error cases or permissions, but the annotations lower the bar.

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?

Two sentences with zero waste. The module clarification is front-loaded, followed by the core action and then a key conditional behavior. Every sentence earns its place and is easy to parse.

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?

Given the presence of an output schema, annotations, and full schema descriptions, the description covers the essential purpose, return value (deviceCode), and conditional behavior. It could mention what to do after receiving the deviceCode, but the polling step is referenced implicitly via 'for polling' and a sibling tool exists.

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 parameters (profile and context_id) are fully documented in the schema. The description does not add any parameter-specific meaning beyond what the schema provides, so the baseline score of 3 applies.

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?

The description states a specific verb ('Start') and resource ('Device Code flow for SSO') and clarifies the module ('aws (not aws-sessions)'). It also mentions the return value (deviceCode) and a conditional behavior, making it easy to distinguish from siblings like aws_sso_login_device_poll or aws_sso_login_global_start.

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 usage by stating 'If a valid session already exists, returns status already_authenticated without starting a new login,' which gives a condition for calling it. However, it does not explicitly name alternatives like aws_sso_login or aws_sso_login_global_start or state when to prefer this tool over them.

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?