Opsphere — DevOps & SRE Intelligence

AWS SSO Login Remoto

aws_sso_login_remote

Start SSO login without opening a browser. Detects the flow type (Device Code vs OAuth PKCE) and returns the necessary information.

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

A3.5/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 safety is partially covered. The description adds that no browser opens and flow type is detected, but it omits the multi-step consequence, such as needing a follow-up poll tool, and does not describe session/token side effects.

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, and the key action plus remote constraint is front-loaded.

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 shape need not be explained. However, for an SSO login starter in a family of start/poll tools, the description does not explain the follow-up step or how the returned flow information maps to the device/global poll siblings, leaving an important workflow gap.

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 profile and context_id are documented in the schema. The description adds no parameter-level meaning beyond that, which is the baseline expectation when the schema is fully described.

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?

States a specific verb and resource: 'Start SSO login,' with the scope 'without opening a browser,' and adds that it detects Device Code versus OAuth PKCE. This distinguishes it from a browser-based sibling, but it does not explicitly name which sibling to use for each detected flow.

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?

Gives a clear usage context (browserless login) but does not say when to use this instead of aws_sso_login, aws_sso_login_device_start, or aws_sso_login_global_start. The agent must infer the routing from the detected flow type.

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?