Opsphere — DevOps & SRE Intelligence

Azure User Login — Start

azure_user_login_start

Starts a device code login flow for a specific Azure tenant. Returns a URL and code the user must visit to authenticate. Only available in user-scoped mode (web chat).

Input Schema

Name	Required	Description
`scopes`	No	OAuth scopes (optional). Defaults to https://management.azure.com/.default only. Do not pass multiple *.default scopes — Entra ID rejects them (ADSTS70011).
`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 credentials). Do NOT pass the MCP tenant slug (e.g. "example-workspace").

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

A3.8/5.0

Behavior4/5

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

Annotations already declare that this is not read-only or destructive, and the description adds useful behavior: it starts a device code flow, returns a URL and code, and requires the user to visit that URL. The user-scoped mode restriction is also meaningful context beyond the annotations, though expiry and polling behavior are not disclosed.

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 three short sentences with no waste. It front-loads the core action, then states the return value and availability constraint.

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?

With annotations, a complete input schema, and an output schema, the description is largely sufficient for correct invocation. Its main omission is not mentioning the necessary follow-up with azure_user_login_poll, which an agent may need in order to complete the login flow.

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 all three optional parameters are already documented in the schema, including scopes and tenant ID details. The description only generally refers to a 'specific Azure tenant' and does not add syntax or meaning beyond the schema.

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 states a specific verb and resource: starting a device code login flow for an Azure tenant. It clearly distinguishes the operation from generic Azure tools, but it does not explicitly differentiate itself from the closely related azure_user_login_poll sibling.

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 gives a clear availability constraint with 'Only available in user-scoped mode (web chat)', which helps an agent know when this tool is usable. However, it provides no explicit alternatives or follow-up guidance, such as when to use azure_user_login_poll after starting the flow.

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?