Opsphere — DevOps & SRE Intelligence

Remove integration credentials

ops_remove_integration

Destructive

Removes all stored credentials for a provider. Your session reconnects automatically afterward.

Input Schema

Name	Required	Description	Default
`provider`	Yes	Provider name to remove all credentials for
`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.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, so the description is not obligated to restate danger. It adds genuine value beyond them by scoping the blast radius ('all stored credentials' for a single provider) and disclosing the post-call side effect ('your session reconnects automatically afterward'). It stops short of saying whether the deletion is recoverable or whether re-authentication is required.

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 short sentences, no preamble, and the scope ('all stored credentials') plus the after-effect are both front-loaded. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Annotations cover the safety profile and an output schema exists, so the description only needs to add scope and consequence — which it does in two sentences. An agent has enough to call it correctly without further prose.

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 both provider and context_id. The phrase 'for a provider' merely echoes the required parameter and adds no syntax, format, or scoping detail, and context_id is not addressed at all. Baseline 3 applies when the schema carries the load.

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: removes all stored credentials for a provider. This clearly distinguishes it from read-only siblings like ops_list_integrations or ops_test_integration, though it does not explicitly contrast with ops_account_unlink, the nearest destructive 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?

Use is implied by the verb (remove credentials) but there is no explicit when-to-use vs. when-not, no mention of the sibling that unlinks accounts, and no warning about when this should be avoided. The agent must infer the trigger condition.

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?