Opsphere — DevOps & SRE Intelligence

Datadog monitor lookup

dd_monitors_lookup

Read-only

Fetch monitor definition/state by id or search query. For all firing monitors use alerts_active, not this tool.

Input Schema

Name	Required	Description
`name`	No	Substring match via title: filter
`limit`	No
`query`	No	Monitor search query
`monitorId`	No	Numeric monitor id
`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.

Changed5 schema fields changedOct 26, 2026

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

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

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

removedOutput schema / properties / data / properties / monitors / items / properties
```
Removed value: -{}
```

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

A4.2/5.0

Behavior3/5

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

The annotations already declare this as a non-destructive, read-only operation, so the safety profile does not need to be restated. The description adds that it fetches monitor definition/state and supports id or search-query lookup, but does not add meaningful behavioral details beyond annotations and purpose, such as pagination behavior or authentication requirements.

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 two concise sentences with the primary purpose front-loaded and the sibling-tool routing stated second. Every sentence earns its place and there is no unnecessary text.

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?

An output schema exists, annotations cover the safety profile, and the schema documents most parameters, so the description is largely complete for an agent to call the tool. The main remaining ambiguity is what happens when no id or query is supplied, since the description implies an id/search-query lookup mode while the schema requires no parameters.

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 80%, so the schema already documents most parameters, including monitorId, query, name, and context_id. The description only echoes the id/search-query distinction and does not add meaning for name, limit, or context_id beyond the structured schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Fetch) and resource (monitor definition/state), and explicitly supports lookup by id or search query. It also distinguishes this tool from the sibling alerts_active, making the tool's purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an explicit exclusion: for all firing monitors, use alerts_active instead of this tool. Combined with the stated id/search-query lookup modes, this tells an agent both when to use this tool and when to choose the alternative.

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?