Opsphere — DevOps & SRE Intelligence

Get your work context

ops_get_work_context

Read-only

Returns operational context configured for your tenant (default account summary plus all cloud accounts). Use when you need full context for a non-default account.

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.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```

changedOutput schema / properties / data / properties / items / items / additionalProperties

Previous value: -trueNew value: +{
+  "type": [
+    "string",
+    "number",
+    "boolean",
+    "null"
+  ]
+}

removedOutput schema / properties / data / properties / items / items / properties
```
Removed value: -{}
```
addedOutput schema / properties / data / properties / payloadJson
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 1,
+  "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=true, destructiveHint=false, and closed-world scope, so the safety profile is covered elsewhere. The description adds what the payload contains (default account summary plus all cloud accounts), which is useful, but says nothing about the tenant scoping rules, what happens if no tenant default exists, or response size. Modest value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with what is returned before the usage note, with no filler. The brevity is close to under-specification given the sibling landscape, but every sentence does carry information.

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 an output schema present, return values need no explanation, and the tool is a simple read-only call with one optional parameter. The one real gap is the unresolved ambiguity about default vs. non-default account selection, which the description raises but does not settle.

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 the single optional context_id parameter is fully documented in the schema, including the ctx_* format and the omit-to-use-active-workspace behavior. The description never mentions context_id, so it adds no meaning beyond the schema; baseline 3 applies.

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 uses a specific verb (returns) and a named resource (operational context configured for your tenant), and clarifies the payload (default account summary plus all cloud accounts). It stops short of distinguishing itself from close siblings like ops_set_work_context or ops_accounts_list, so the agent must still infer the boundary between read vs. set.

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?

It offers one when-to-use cue ("Use when you need full context for a non-default account"), but no alternatives or exclusions are named, and the cue sits in tension with the schema note that omitting context_id uses the active workspace. The agent is left to reconcile which situation actually selects this tool over ops_set_work_context.

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?