Opsphere — DevOps & SRE Intelligence

AWS SSO Global Poll

aws_sso_login_global_poll

Poll in batch the status of multiple AWS SSO global device_codes and return aggregated status (success|pending|partial|error).

Input Schema

Name	Required	Description	Default
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`device_codes`	Yes	Lista de device_code devueltos por aws_sso_login_global_start.

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.4/5.0

Behavior1/5

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

The description frames the operation as polling status and returning aggregated status, which strongly implies a read-only check. The annotations declare readOnlyHint=false, creating an annotation contradiction: an agent cannot tell whether this polling has side effects or state-changing behavior.

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?

One front-loaded sentence states the action, resource, batch scope, and aggregated return values. There is no wasted text.

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?

For a two-parameter polling tool with an output schema, the description is largely complete: it says what is polled and what status classes are returned. It omits when-to-use guidance and any side-effect disclosure, but return-value detail is appropriately left to the output schema.

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 the schema already documents device_codes and context_id. The description reinforces that multiple device_codes are processed in batch, but adds no format, source, or handling details beyond the schema.

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 specific verb and resource: poll the status of multiple AWS SSO global device_codes. The batch/global scope distinguishes it from single-device SSO polling tools without needing the sibling name.

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?

Implies usage by saying it polls multiple device_codes in batch, which suggests use after a global login start. However it does not explicitly state when to use it versus aws_sso_login_device_poll or other SSO siblings, nor does it list prerequisites or exclusions.

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?