Skip to main content
Glama

notolens

by com.notolens
OverviewDiscussionsAdmin

Add asset

add_asset

Add an asset to a monitor: an official domain to watch for conflicting registrations, a mark text for trademark office filings, or a brand keyword for app store listings. This is confirmed work: confirm true records that the user approved the exact type, value, config and reference choice, because the first scan is scheduled as soon as the asset exists and archiving (dashboard-only) only stops future scans, it does not undo a scan that already completed. Required config per type: domain needs config.brand, trademark needs config.offices (subset of US, EM; classes optional, Nice 1-45), app needs config.stores (subset of google_play, app_store). Domain assets also need an explicit reference choice (capture, upload or skip); trademark and app accept an optional upload staged with prepare_asset_upload. A capture always goes through preview_domain: its capture_token makes the stored baseline exactly the render the user approved, and the response includes that screenshot as image content. When the preview produced no screenshot (captured false), upload or skip are the choices; a capture_token from such a preview stores only the site icon. site_result carries the probe outcome recorded at preview time. For domain assets, the response's match_scope reports the matching scope: 'distinctive' names are matched across TLDs while 'generic' common terms are only watched on the asset's own suffix. On an active monitor the first scan starts right away (list_scans shows it); next_scan_at reports the next scheduled scan, null while that first scan is still running or the monitor is paused. Errors name the cause: invalid input, plan limit reached, or a duplicate already watched by the monitor.

Input Schema

NameRequiredDescriptionDefault
typeYesAsset type: domain, trademark or app.
valueYesWhat to watch: the official domain for type domain (e.g. "acme.com"), the mark or brand text for trademark, the brand keyword for app.
configNoType-specific options: brand (required for domain), offices (required for trademark: subset of US, EM), classes (optional Nice classes 1-45, trademark only), stores (required for app: subset of google_play, app_store).
confirmYesRequired. true records that the user explicitly confirmed the exact asset: its type, value, config and reference choice, knowing the first scan is scheduled right away.
referenceNoVisual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (upload or skip are the choices when the preview produced no screenshot, captured false). Optional for trademark and app; only upload applies there (mark image or app icon).
monitor_idYesMonitor id from list_monitors or create_monitor.

Output Schema

NameRequiredDescriptionDefault
assetYes
site_resultYes
next_scan_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / asset / properties / id
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / asset / required
      Previous value: -[
-  "id",
-  "monitor_id",
-  "type",
-  "value",
-  "status",
-  "label",
-  "scope",
-  "cadence",
-  "match_scope",
-  "classes",
-  "last_checked_at",
-  "has_reference",
-  "dashboard_url",
-  "reference_stored"
-]New value: +[
+  "monitor_id",
+  "type",
+  "value",
+  "status",
+  "label",
+  "scope",
+  "cadence",
+  "match_scope",
+  "classes",
+  "last_checked_at",
+  "has_reference",
+  "dashboard_url",
+  "reference_stored"
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / reference / description
      Previous value: -"Visual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (the remaining choice when the preview rendered nothing, captured false). Optional for trademark and app; only upload applies there (mark image or app icon)."New value: +"Visual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (upload or skip are the choices when the preview produced no screenshot, captured false). Optional for trademark and app; only upload applies there (mark image or app icon)."
    • addedOutput schema / properties / asset / 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 / asset / required
      Previous value: -[
-  "id",
-  "monitor_id",
-  "type",
-  "value",
-  "status",
-  "label",
-  "scope",
-  "cadence",
-  "match_scope",
-  "last_checked_at",
-  "has_reference",
-  "dashboard_url",
-  "reference_stored"
-]New value: +[
+  "id",
+  "monitor_id",
+  "type",
+  "value",
+  "status",
+  "label",
+  "scope",
+  "cadence",
+  "match_scope",
+  "classes",
+  "last_checked_at",
+  "has_reference",
+  "dashboard_url",
+  "reference_stored"
+]
  3. Changed1 schema field changed
    • changedOutput schema / properties / site_result / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "ok",
-      "unreachable",
-      "blocked"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "ok",
+      "http_error",
+      "unreachable",
+      "blocked"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  4. Changed2 schema fields changed
    • changedInput schema / properties / config / description
      Previous value: -"Type-specific options: brand (required for domain), offices (required for trademark: subset of US, EM, WO), classes (optional Nice classes 1-45, trademark only), stores (required for app: subset of google_play, app_store)."New value: +"Type-specific options: brand (required for domain), offices (required for trademark: subset of US, EM), classes (optional Nice classes 1-45, trademark only), stores (required for app: subset of google_play, app_store)."
    • changedInput schema / properties / reference / description
      Previous value: -"Visual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (use it when the preview rendered nothing, captured false). Optional for trademark and app; only upload applies there (mark image or app icon)."New value: +"Visual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (the remaining choice when the preview rendered nothing, captured false). Optional for trademark and app; only upload applies there (mark image or app icon)."
  5. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Required. Set true only after the user has explicitly confirmed the exact asset: its type, value, config and reference choice, knowing the first scan is scheduled right away."New value: +"Required. true records that the user explicitly confirmed the exact asset: its type, value, config and reference choice, knowing the first scan is scheduled right away."
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: the first scan is scheduled as soon as the asset exists, archiving (dashboard-only) stops only future scans and cannot undo a completed scan, and errors name their cause (invalid input, plan limit, duplicate). This is exactly the irreversible-side-effect context the destructiveHint=false annotation alone does not convey.

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?

Purpose is front-loaded and almost every sentence carries behavioral weight, but it is a dense run-on paragraph that repeats some schema-documented config requirements and mixes upstream-step guidance with response-field explanation. Tighter grouping would improve scanability.

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?

For a 6-parameter, multi-type mutation tool with an output schema, the description covers the confirm gate, the per-type requirements, the side-effect timing, and even response fields (match_scope, site_result, next_scan_at, image content). Nothing an agent needs to invoke it correctly appears to be missing.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning: per-type config requirements (domain→brand, trademark→offices with classes optional, app→stores), the reference choice taxonomy, and the subtle case where a capture_token from a no-screenshot preview stores only the site icon. That extra nuance lifts it above baseline.

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?

States a specific verb and resource ('Add an asset to a monitor') and immediately enumerates the three asset types with what each watches (domain for conflicting registrations, mark text for trademark filings, brand keyword for app store listings). An agent can tell exactly which tool this is and what it produces without opening the schema.

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?

Explicit when-to-use rules: confirm=true requires prior user approval, and the description routes the agent to preview_domain (capture_token) and prepare_asset_upload (upload_token) as upstream steps, including the fallback to upload/skip when a preview produced no screenshot. The alternatives and the conditions that select them are stated, not inferred.

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

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