Skip to main content
Glama

notolens

by com.notolens
OverviewDiscussionsAdmin

Create monitor

create_monitor

Create a monitor: the container that watches one brand's conflicting domain registrations, trademark filings and app listings. Its name is the brand it watches. The monitor starts empty and dormant; add_asset adds assets one at a time, and the first scan starts on its own. An organization without a plan (a null plan in get_account) can create its first monitor and save its brand description, while assets need a plan. Plan limits apply and the error names the limit that was hit.

Input Schema

NameRequiredDescriptionDefault
nameYesThe brand or company name.

Output Schema

NameRequiredDescriptionDefault
monitorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / monitor / 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 / monitor / 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 / monitor / required
      Previous value: -[
-  "id",
-  "name",
-  "status",
-  "next_scan_at",
-  "brand_context",
-  "dashboard_url"
-]New value: +[
+  "id",
+  "name",
+  "status",
+  "next_scan_at",
+  "brand_description",
+  "dashboard_url"
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / monitor / 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 / monitor / required
      Previous value: -[
-  "id",
-  "name",
-  "status",
-  "next_scan_at",
-  "dashboard_url"
-]New value: +[
+  "id",
+  "name",
+  "status",
+  "next_scan_at",
+  "brand_context",
+  "dashboard_url"
+]
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered; the description adds value on top by disclosing the lifecycle side effect (dormant on creation, first scan auto-starts once assets exist) and the plan-limit failure mode with a limit-naming error. That is exactly the non-obvious behavior an agent needs before calling a mutating tool.

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?

Four short sentences, front-loaded with the definition, then the lifecycle, then the plan precondition. Every sentence carries distinct information — no restatement of the title or annotations — and it ends on the failure mode, which is where an agent's attention belongs.

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?

The tool is simple (one required parameter) and has an output schema, so return values need no explanation. Combined with annotations and full schema coverage, the description supplies the only things still missing: what a monitor represents, its dormant starting state, and the plan constraint that determines success.

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% on the single `name` parameter and the schema already says 'The brand or company name.' The description still adds real meaning by explaining that the monitor's name *is* the brand it watches, which tells the agent what value to supply rather than just its type. It does not cover length constraints, but those belong to the 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?

States a specific verb and resource ('Create a monitor') and immediately defines what a monitor is — a container watching one brand's conflicting domain registrations, trademark filings and app listings. It also pins down the naming semantics ('Its name is the brand it watches'), which distinguishes create_monitor from list_monitors, update_monitor and add_asset without the agent opening any schema.

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

Usage Guidelines4/5

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

Gives concrete preconditions and routing: the monitor starts empty and dormant, assets are added one at a time via add_asset, and the first scan begins on its own. It also spells out the plan gating ('an organization without a plan ... can create its first monitor ... while assets need a plan'), which tells the agent when this call will succeed versus fail. It stops short of an explicit negative rule (e.g. use update_monitor to rename an existing monitor), so not a 5.

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