Skip to main content
Glama
Sign In

Opsphere — DevOps & SRE Intelligence

by io.opsphere.mcp-cursor
OverviewDiscussionsAdmin

Latest deployment status (multi-platform)

deployment_status
Read-only

Multi-stack deployment status: Vercel, CI (Bitbucket/GHE/GitLab), ArgoCD GitOps, S3+CloudFront, ECS. Resolves sources from cloud catalog (vercel_project, argocd_*, deployment_sources JSON). Use target to qualify the catalog account/product; scope=auto queries all configured sources.

Input Schema

NameRequiredDescriptionDefault
envNoEnvironment slug or label (e.g. PRD, int). Defaults to catalog default environment.
scopeNoWhich deployment platforms to queryauto
targetNoCloud Catalog account or product qualifier (slug, name, alias, or detection pattern). Required when the tenant has multiple accounts sharing the same env (e.g. prd) — otherwise the tool returns candidates.
context_idNoOptional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.

Output Schema

NameRequiredDescriptionDefault
okYes
dataYes
contractVersionYes
dataSchemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / target / description
      Previous value: -"Cloud Catalog account or product qualifier (slug, name, alias, or detection pattern)."New value: +"Cloud Catalog account or product qualifier (slug, name, alias, or detection pattern). Required when the tenant has multiple accounts sharing the same env (e.g. prd) — otherwise the tool returns candidates."
    • addedOutput schema / properties / data / properties / candidates
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / dataSchemaVersion
      Added value: +{
+  "const": 1,
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses that sources are resolved from a cloud catalog via vercel_project, argocd_*, and deployment_sources JSON, and that scope=auto fans out across all configured sources — useful for understanding what a call actually touches.

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?

Three dense sentences, front-loaded with the platform list so the agent knows the scope immediately. The catalog key names (vercel_project, argocd_*, deployment_sources JSON) are compact shorthand that earns its place by explaining source resolution, though the paragraph is information-dense for a single read.

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 not be described, and all four parameters are documented in the schema. The description covers platform coverage, catalog resolution, and scope fan-out; it could still say what happens when a source fails or how results are aggregated across stacks, but nothing critical is missing for a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns above baseline by explaining that scope=auto means "query all configured sources" and that target qualifies the catalog account/product. It adds interpretive meaning on top of the schema rather than restating it.

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+resource ("deployment status") and distinguishes itself from the many single-platform siblings by enumerating the stacks it aggregates: Vercel, CI (Bitbucket/GHE/GitLab), ArgoCD GitOps, S3+CloudFront, ECS. It never names an alternative sibling explicitly, so an agent must infer that vercel_deploys_latest/vercel_project_status are the narrower single-stack equivalents.

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?

Gives operational direction ("scope=auto queries all configured sources", "Use target to qualify the catalog account/product"), but these are parameter hints rather than when-to-use guidance. There is no statement of when to pick this over vercel_project_status or env_health_summary, so usage context is only implied.

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 toolsInspect
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