Skip to main content
Glama

Create monitor

create_monitor

Create a monitor: the container that watches one brand's conflicting domain registrations, trademark filings, app listings and search ads. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_monitor"
  }
}

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.4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false. The description adds genuinely non-structured behavior: the monitor starts empty and dormant, the first scan triggers automatically, and plan limits produce an error that names the limit hit. It leaves one gap — nothing about what happens on duplicate name creation (relevant given idempotentHint=false) — but the added lifecycle and error semantics are substantive.

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 sentences, all information-dense, with the resource definition front-loaded before lifecycle and plan caveats. No filler, though the final plan-limits sentence is slightly compressed and could be split for 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 one-parameter create tool with a rich output schema, this covers everything an agent needs: what is created, what it starts as, how to populate it, what the auto-trigger is, and the plan gating that can cause failure. Return values are correctly left to the output schema.

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 a single parameter and 100% schema coverage, the baseline is 3. The description earns above baseline by explaining that the name value functions as the brand identity the monitor watches, which is a semantic constraint the schema's 'The brand or company name' does not convey.

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 gives a specific verb (create) and defines the resource functionally — 'the container that watches one brand's conflicting domain registrations, trademark filings, app listings and search ads' — which is far more distinctive than the title 'Create monitor'. It also clarifies that the name IS the brand being watched, so agent's mental model is unambiguous.

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?

It routes the agent forward explicitly: 'add_asset adds assets one at a time' and 'the first scan starts on its own', so the agent knows not to look for a separate start-scan tool. It states a real prerequisite (an organization without a plan can still create its first monitor), though it doesn't contrast this with update_monitor for existing brands.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources