Skip to main content
Glama
nyku

Competiflow MCP Server

by nyku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update monitor

update_monitor
Idempotent

Modify one monitor's URL, type, check cadence, active/paused status, or minimum severity; pause checks while keeping history. Use update_competitor to change all monitors for a competitor.

Instructions

Change one monitor's URL, type, cadence, status, or min_severity. Use status paused to stop checks and keep history. To change every monitor of a competitor at once, use update_competitor.

Input Schema

NameRequiredDescriptionDefault
urlNoNew URL to watch
statusNoactive runs checks; paused stops checks and keeps history
cadenceNoCheck frequency. Faster cadences use more monthly checks; plans set a minimum (422 cadence_not_allowed).
monitor_idYesMonitor id from list_monitors or list_competitors
min_severityNoChanges below this severity are not reported
monitor_typeNoKind of page: homepage, blog, docs, changelog, or pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.1
    • addedInput schema / properties / cadence / description
      Added value: +"Check frequency. Faster cadences use more monthly checks; plans set a minimum (422 cadence_not_allowed)."
    • addedInput schema / properties / min_severity / description
      Added value: +"Changes below this severity are not reported"
    • addedInput schema / properties / monitor_id / description
      Added value: +"Monitor id from list_monitors or list_competitors"
    • addedInput schema / properties / monitor_type / description
      Added value: +"Kind of page: homepage, blog, docs, changelog, or pricing"
    • addedInput schema / properties / monitor_type / enum
      Added value: +[
+  "homepage",
+  "blog",
+  "docs",
+  "changelog",
+  "pricing"
+]
    • addedInput schema / properties / status / description
      Added value: +"active runs checks; paused stops checks and keeps history"
    • addedInput schema / properties / url / description
      Added value: +"New URL to watch"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description adds real context beyond them by explaining that setting status to paused halts checks but preserves history, which is the main side effect an agent needs to reason about. It doesn't say whether omitted fields keep their current values, but nothing contradicts the annotations.

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 short sentences, front-loaded with the resource and mutable fields, then a status-specific rule, then a sibling pointer. No filler; 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?

For a partial-update mutation with full schema coverage and a non-destructive idempotent annotation profile, the description covers scope, alternative routing, and the key status side effect. Only gap is whether unmentioned fields are left untouched on a partial update, which is a minor omission here.

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 100%, with enums and per-parameter notes (including the 422 cadence_not_allowed case), so the schema carries the semantics. The description only restates the field list and duplicates the paused explanation, adding little new meaning beyond structured data.

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 (change) plus the exact set of mutable fields on a single monitor, and explicitly distinguishes itself from the bulk sibling update_competitor. An agent can tell it apart from create_monitor/delete_monitor without 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?

Names the alternative tool and the condition that selects it ("To change every monitor of a competitor at once, use update_competitor"). Also gives a concrete usage rule for the status field (pause to stop checks while keeping history). No explicit when-not-to-use, but the routing guidance is clear.

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

Deploy Server

Other Tools