Opsphere — DevOps & SRE Intelligence

Azure User Login — Poll

azure_user_login_poll

Checks whether the device code login initiated by azure_user_login_start has completed. Returns status: "completed" when the token is stored and ready.

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.
`azure_tenant_id`	No	Azure AD directory GUID (optional — defaults to azure.tenant_id from tenant config)

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 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"
+}
```

removedOutput schema / properties / data / properties / format

Removed value: -{
-  "enum": [
-    "plain",
-    "markdown",
-    "json"
-  ],
-  "type": "string"
-}

addedOutput schema / properties / data / properties / message
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / pollIntervalSeconds
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / data / properties / status

Added value: +{
+  "enum": [
+    "pending",
+    "completed",
+    "failed"
+  ],
+  "type": "string"
+}

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"
+}
```

changedOutput schema / properties / data / required

Previous value: -[
-  "text"
-]New value: +[
+  "status"
+]

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

Behavior3/5

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

The annotations declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description does not need to carry the full behavioral burden. It adds useful context that 'completed' means the token is stored and ready, but it does not explain polling frequency, intermediate statuses, or why the operation is not marked read-only.

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 two short sentences and is front-loaded with the core purpose. The second sentence adds a precise completion condition rather than restating the schema.

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 simple polling tool with an output schema, fully documented parameters, and annotations covering safety, the description provides the essential prerequisite and completion meaning. It could be more complete by stating whether the agent should repeatedly poll until completion, but nothing critical to correct invocation is missing.

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%, and both parameters are optional, so the schema already documents their meanings and defaults. The description adds no parameter-specific guidance, making the baseline score appropriate.

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 uses a specific verb and resource: it checks whether the device code login initiated by azure_user_login_start has completed. It explicitly ties itself to that sibling, so an agent can distinguish it from the login-start tool without opening the 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?

The description clearly establishes the prerequisite context: this tool is for a device code login initiated by azure_user_login_start. It does not, however, explicitly say when to choose this over azure_user_session_status or how often to poll, so some usage details remain inferred.

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?