Opsphere — DevOps & SRE Intelligence

Test integration credentials

ops_test_integration

Read-only

Performs a lightweight API call to verify that stored credentials for a provider are valid. Credential values are never returned — only pass/fail.

Input Schema

Name	Required	Description
`env`	No	Cloud catalog environment slug (Algolia multi-env). Tests Application ID + {env}:api_key from Cloud Catalog.
`profile`	No	AWS Cloud Catalog aws_profile or account slug (required when multiple AWS accounts exist).
`provider`	Yes	Provider name to test 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.8/5.0

Behavior4/5

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

Annotations already establish readOnly=true, destructive=false, openWorld=false, so the safety profile is covered. The description adds meaningful context beyond them: it is a lightweight call and credential values are never returned, only pass/fail, which reassures an agent about secret exposure. It stops short of saying how failures surface (error vs. fail result), keeping it at 4.

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 tightly written sentences with zero waste, and the core purpose is front-loaded before the security guarantee.

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 rich 100%-covered schema, and an output schema, the description covers what an agent needs to call it correctly. The only small gap is not stating whether an invalid credential raises an error or returns a fail verdict.

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 provider, env, profile, and context_id are already documented in the schema. The description adds no parameter-level meaning, so the 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?

States a specific verb and resource: performs a lightweight API call to verify stored credentials for a provider. It is clearly distinguishable from ops_configure_integration and ops_remove_integration by implication, though it never names those siblings explicitly.

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?

Usage is only implied – an agent can infer this is the post-configuration validation step, but the description gives no explicit when/when-not conditions or pointer to configure/list/remove alternatives in the sibling set.

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?