notolens

List monitors

list_monitors

Read-only

List the organization's brand monitors. Each monitor watches domains, trademark offices and app stores for conflicts with one brand. Only active assets are listed; archived ones are hidden, same as the dashboard.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`monitors`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026

removedOutput schema / properties / monitors / items / properties / assets / items / properties / id
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / monitors / items / properties / assets / items / required

Previous value: -[
-  "id",
-  "monitor_id",
-  "type",
-  "value",
-  "status",
-  "label",
-  "scope",
-  "cadence",
-  "match_scope",
-  "classes",
-  "last_checked_at",
-  "has_reference",
-  "dashboard_url"
-]New value: +[
+  "monitor_id",
+  "type",
+  "value",
+  "status",
+  "label",
+  "scope",
+  "cadence",
+  "match_scope",
+  "classes",
+  "last_checked_at",
+  "has_reference",
+  "dashboard_url"
+]

Changed3 schema fields changedOct 16, 2026

removedOutput schema / properties / monitors / items / properties / brand_context

Removed value: -{
-  "description": "The user's own background about the brand (what it sells, to whom and where, the companies, sites and partners it operates with); null when not set. Assessments read it; it never limits which subjects are found.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

addedOutput schema / properties / monitors / items / properties / brand_description

Added value: +{
+  "description": "The user's own background about the brand (what it sells, to whom and where, the companies, sites and partners it operates with); null when not set. Assessments read it; it never limits which subjects are found.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / monitors / items / required

Previous value: -[
-  "id",
-  "name",
-  "status",
-  "pause_reason",
-  "next_scan_at",
-  "brand_context",
-  "dashboard_url",
-  "assets"
-]New value: +[
+  "id",
+  "name",
+  "status",
+  "pause_reason",
+  "next_scan_at",
+  "brand_description",
+  "dashboard_url",
+  "assets"
+]

Changed2 schema fields changedOct 16, 2026

addedOutput schema / properties / monitors / items / properties / brand_context

Added value: +{
+  "description": "The user's own background about the brand (what it sells, to whom and where, the companies, sites and partners it operates with); null when not set. Assessments read it; it never limits which subjects are found.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / monitors / items / required

Previous value: -[
-  "id",
-  "name",
-  "status",
-  "pause_reason",
-  "next_scan_at",
-  "dashboard_url",
-  "assets"
-]New value: +[
+  "id",
+  "name",
+  "status",
+  "pause_reason",
+  "next_scan_at",
+  "brand_context",
+  "dashboard_url",
+  "assets"
+]

Changed2 schema fields changedOct 16, 2026

addedOutput schema / properties / monitors / items / properties / assets / items / properties / classes

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Nice classes of a trademark asset, empty when none were set; null for other types. Classes inform the assessment and never limit which filings are found."
+}

changedOutput schema / properties / monitors / items / properties / assets / items / required

Previous value: -[
-  "id",
-  "monitor_id",
-  "type",
-  "value",
-  "status",
-  "label",
-  "scope",
-  "cadence",
-  "match_scope",
-  "last_checked_at",
-  "has_reference",
-  "dashboard_url"
-]New value: +[
+  "id",
+  "monitor_id",
+  "type",
+  "value",
+  "status",
+  "label",
+  "scope",
+  "cadence",
+  "match_scope",
+  "classes",
+  "last_checked_at",
+  "has_reference",
+  "dashboard_url"
+]

First observedOct 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds a genuinely non-obvious behavioral fact: archived monitors are filtered out, matching the dashboard. It does not mention ordering or pagination, but the output schema covers return values.

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?

Three sentences, no waste, front-loaded with the action and scope before the explanatory and filtering details. Every sentence earns its place.

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 zero parameters, an output schema, and annotations covering the safety profile, the description is nearly complete for this tool. The only omission is any note on result ordering or pagination, which is minor for a no-parameter list endpoint.

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?

The tool takes zero parameters, so the baseline is 4. Nothing in the schema needs clarifying text, and the description introduces no parameter-related ambiguity.

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 ("List the organization's brand monitors") and adds domain semantics about what a monitor watches. The read-only listing verb implicitly separates it from create_monitor/update_monitor, but no sibling is named, so differentiation is left to inference.

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 you call this to enumerate monitors. There is no explicit when-to-use, when-not, or pointer to alternatives such as list_matches or get_account for related data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All notolens 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?