Skip to main content
Glama
nyku

Competiflow MCP Server

by nyku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create monitor

create_monitor

Watch a specific competitor page, such as pricing or docs, that discovery missed by setting the URL, page type, and check cadence.

Instructions

Watch one specific page of an existing competitor, such as a pricing or docs URL that discovery missed. To add a new competitor and discover its pages automatically, use add_competitor.

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL of the page to watch
cadenceNoCheck frequency. Faster cadences use more monthly checks; plans set a minimum (422 cadence_not_allowed).
monitor_typeYesKind of page: homepage, blog, docs, changelog, or pricing
competitor_idYesCompetitor id from list_competitors or add_competitor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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 / competitor_id / description
      Added value: +"Competitor id from list_competitors or add_competitor"
    • 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 / url / description
      Added value: +"Full URL of the page to watch"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and, importantly, idempotentHint=false. The description adds that the competitor must already exist, which is useful precondition context, but it does not explain what happens on duplicate calls (given non-idempotency) or what creating a monitor returns.

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?

Two sentences, the core capability is front-loaded, and the second sentence is purely a routing rule. No filler.

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 mutation with no output schema, the annotations plus full schema coverage cover most of what an agent needs. The remaining gap is what creation produces and how duplicates behave given idempotentHint=false, which the description never addresses.

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 coverage is 100% and the cadence and monitor_type parameters carry enums plus their own cost/quota notes, so the schema does the heavy lifting. The description only contextualizes the url parameter implicitly ('one specific page'); baseline 3 applies.

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 — watch one page of an existing competitor — and immediately scopes it with example page types (pricing, docs). It explicitly distinguishes itself from add_competitor, so an agent can route correctly without opening a 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?

Names the alternative (add_competitor) and the exact condition that selects it: when the competitor is new and pages must be discovered. It also implies when-not for this tool (pages discovery already found) via 'that discovery missed.'

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