Skip to main content
Glama
Sign In

FluxProof

by io.github.equinoxaifinance-rgb
OverviewDiscussionsAdmin

Start watching a page

fluxproof_create_monitor

Create a monitor using a buyer-owned FluxProof API key. Creates persistent state and performs a baseline check, consuming quota. Not idempotent: each call creates a new monitor.

Input Schema

NameRequiredDescriptionDefault
urlYesRequired: the full address of one public web page, for example https://example.com/ or https://store.example.com/products/item; a bare domain such as example.com also works. Not a search phrase, product name or placeholder. No sign-in, cookies, browser rendering or private-network targets.
partNoOptional: watch only part of the page. start is text on the first line of the part (2–120 characters, any case); end is text on its last line, or lines (1–200, default 20) sets its length. Only that part is compared; the saved copy is still the whole page.
labelNoOptional human-readable monitor label, up to 120 characters.
api_keyNoBuyer-owned FluxProof API key; a secret credential.
alert_whenNoOptional conditions on the watched part: contains (alert when this text appears) and/or missing (alert when this text disappears), 2–120 characters each. A condition that becomes true is a high-significance change.
watch_termsNoOptional terms to track, each 2–80 characters; at most 20 distinct terms.
webhook_urlNoOptional public HTTPS webhook receiver; paid pass required. Delivery is signed and can occur when checks run. A Slack or Discord incoming-webhook address gets a readable chat message instead of the JSON payload.
interval_minutesNoRequested schedule in minutes. Free keys use 1440 (daily); paid passes have a 15-minute minimum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Required: the full address of one public web page, for example https://example.com/ or https://store.example.com/products/item. Not a search phrase or product name. No sign-in, cookies, browser rendering or private-network targets."New value: +"Required: the full address of one public web page, for example https://example.com/ or https://store.example.com/products/item; a bare domain such as example.com also works. Not a search phrase, product name or placeholder. No sign-in, cookies, browser rendering or private-network targets."
  2. Changed2 schema fields changed
    • addedInput schema / properties / alert_when
      Added value: +{
+  "additionalProperties": false,
+  "description": "Optional conditions on the watched part: contains (alert when this text appears) and/or missing (alert when this text disappears), 2–120 characters each. A condition that becomes true is a high-significance change.",
+  "properties": {
+    "contains": {
+      "type": "string"
+    },
+    "missing": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / part
      Added value: +{
+  "additionalProperties": false,
+  "description": "Optional: watch only part of the page. start is text on the first line of the part (2–120 characters, any case); end is text on its last line, or lines (1–200, default 20) sets its length. Only that part is compared; the saved copy is still the whole page.",
+  "properties": {
+    "end": {
+      "type": "string"
+    },
+    "lines": {
+      "type": "integer"
+    },
+    "start": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "start"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / webhook_url / description
      Previous value: -"Optional public HTTPS webhook receiver; paid pass required. Delivery is signed and can occur when checks run."New value: +"Optional public HTTPS webhook receiver; paid pass required. Delivery is signed and can occur when checks run. A Slack or Discord incoming-webhook address gets a readable chat message instead of the JSON payload."
  4. Changed2 schema fields changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Buyer-owned FluxProof API key. Treat as a secret: do not include in transcripts, public logs or support messages."New value: +"Buyer-owned FluxProof API key; a secret credential."
    • changedInput schema / properties / url / description
      Previous value: -"Public HTTP(S) page URL. No sign-in, cookies, browser rendering or private-network targets."New value: +"Required: the full address of one public web page, for example https://example.com/ or https://store.example.com/products/item. Not a search phrase or product name. No sign-in, cookies, browser rendering or private-network targets."
  5. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "api_key",
-  "url"
-]New value: +[
+  "url"
+]
  6. Changed6 schema fields changed
    • addedInput schema / properties / api_key / description
      Added value: +"Buyer-owned FluxProof API key. Treat as a secret: do not include in transcripts, public logs or support messages."
    • addedInput schema / properties / interval_minutes / description
      Added value: +"Requested schedule in minutes. Free keys use 1440 (daily); paid passes have a 15-minute minimum."
    • addedInput schema / properties / label / description
      Added value: +"Optional human-readable monitor label, up to 120 characters."
    • addedInput schema / properties / url / description
      Added value: +"Public HTTP(S) page URL. No sign-in, cookies, browser rendering or private-network targets."
    • addedInput schema / properties / watch_terms / description
      Added value: +"Optional terms to track, each 2–80 characters; at most 20 distinct terms."
    • addedInput schema / properties / webhook_url / description
      Added value: +"Optional public HTTPS webhook receiver; paid pass required. Delivery is signed and can occur when checks run."
  7. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: it performs a baseline check, consumes quota, and creates persistent state. 'Not idempotent' merely restates idempotentHint=false, so it earns no extra credit, and it says nothing about failure behavior for an invalid or unreachable URL.

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 sentences, zero filler, and the operative facts (credential, persistent state, quota cost, non-idempotency) are front-loaded. Each sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, nested-object creation tool with no output schema, the definition never says what is returned or how the created monitor is subsequently referenced by check_now, list_changes, or offer. That identifier gap is significant for a state-creating tool, though the input side is fully covered by the schema.

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%, so every parameter including the nested part and alert_when objects is already documented with constraints. The description only echoes the API-key parameter, adding no semantics beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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') plus the key prerequisite ('buyer-owned FluxProof API key'), so the agent knows exactly what the tool does. However, it never distinguishes itself from siblings like fluxproof_preflight or fluxproof_get_free_key, which an agent would plausibly need first.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: mentioning a buyer-owned API key and quota consumption signals this is a billable, credentialed operation. There is no explicit when-to-use/when-not guidance and no routing to alternatives such as checking a URL with fluxproof_preflight before committing to a persistent monitor.

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

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