Skip to main content
Glama

Saber

by app.saber.mcp
OverviewDiscussionsAdmin

monitors-update

Update a monitor

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monitorIdYes
__requestBodyYesRequest body

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / __requestBody / properties / checks / items / properties / type / enum
      Previous value: -[
-  "job_posted",
-  "social_posted",
-  "funding_raised",
-  "investment_made",
-  "ipo_announced",
-  "ipo_stage_changed",
-  "repo_engaged",
-  "ipo_rumoured"
-]New value: +[
+  "job_posted",
+  "social_posted",
+  "funding_raised",
+  "investment_made",
+  "ipo_announced",
+  "ipo_stage_changed",
+  "repo_engaged",
+  "ipo_rumoured",
+  "tender_published"
+]
    • changedInput schema / properties / __requestBody / properties / webhook / properties / intervalSignalLimit / description
      Previous value: -"Maximum signals to deliver per polling interval. Each run delivers at most this many. Over a billing cycle the monitor delivers at most this value times the number of runs its interval allows in the cycle, then waits for the next cycle. When runs overlap, for example a manual trigger during a scheduled run, the cycle total can exceed this by at most one run's limit per overlapping run. For ipo_stage_changed, ipo_rumoured and repo_engaged, which Saber checks every few minutes on its own schedule, the limit bounds each check rather than each interval, and the billing-cycle bound is the effective ceiling."New value: +"Maximum signals to deliver per polling interval. Each run delivers at most this many. Over a billing cycle the monitor delivers at most this value times the number of runs its interval allows in the cycle, then waits for the next cycle. When runs overlap, for example a manual trigger during a scheduled run, the cycle total can exceed this by at most one run's limit per overlapping run. For ipo_stage_changed, ipo_rumoured, repo_engaged and tender_published, which Saber checks on its own schedule (every few minutes, or every hour for tender_published), the limit bounds each check rather than each interval, and the billing-cycle bound is the effective ceiling."
  2. Changed3 schema fields changed
    • addedInput schema / properties / __requestBody / properties / webhook / properties / intervalSignalLimit / description
      Added value: +"Maximum signals to deliver per polling interval. Each run delivers at most this many. Over a billing cycle the monitor delivers at most this value times the number of runs its interval allows in the cycle, then waits for the next cycle. When runs overlap, for example a manual trigger during a scheduled run, the cycle total can exceed this by at most one run's limit per overlapping run. For ipo_stage_changed, ipo_rumoured and repo_engaged, which Saber checks every few minutes on its own schedule, the limit bounds each check rather than each interval, and the billing-cycle bound is the effective ceiling."
    • addedInput schema / properties / __requestBody / properties / webhook / properties / url / description
      Added value: +"Delivery endpoint. Omit it to create a monitor with no delivery: signals are still detected, stored and charged, and are read back from GET /v1/monitors/{monitorId}/signals instead of being POSTed. A url-less webhook block is still accepted, and is how a caller sets interval and intervalSignalLimit without configuring delivery."
    • removedInput schema / properties / __requestBody / properties / webhook / required
      Removed value: -[
-  "url"
-]
  3. Changed1 schema field changed
    • changedInput schema / properties / __requestBody / properties / checks / items / properties / type / enum
      Previous value: -[
-  "job_posted",
-  "social_posted",
-  "funding_raised",
-  "investment_made",
-  "ipo_announced",
-  "ipo_stage_changed",
-  "repo_engaged"
-]New value: +[
+  "job_posted",
+  "social_posted",
+  "funding_raised",
+  "investment_made",
+  "ipo_announced",
+  "ipo_stage_changed",
+  "repo_engaged",
+  "ipo_rumoured"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / __requestBody / properties / checks / items / properties / type / enum
      Previous value: -[
-  "job_posted",
-  "social_posted",
-  "funding_raised",
-  "investment_made",
-  "ipo_announced",
-  "ipo_stage_changed"
-]New value: +[
+  "job_posted",
+  "social_posted",
+  "funding_raised",
+  "investment_made",
+  "ipo_announced",
+  "ipo_stage_changed",
+  "repo_engaged"
+]
  5. Added

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the agent knows this is a non-idempotent write with no annotation contradiction. The description adds nothing on top: it does not say whether the update replaces or merges fields, which fields are immutable (the schema notes check 'type is immutable'), or what permissions are required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words is technically waste-free, but the sizing is grossly disproportionate to a nested mutation tool with checks, target, webhook and schedule blocks. This is under-specification masquerading as brevity, the same pattern the calibration penalized for 'Process'.

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

Completeness2/5

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

For a mutation endpoint with deeply nested objects and no output schema, an agent needs to know what the update replaces, which nested fields are required, and how partial updates behave. Annotations cover only the safety profile, leaving the description with essentially nothing to work with.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%, and the two top-level parameters (monitorId, __requestBody) are undocumented in the description. All meaningful semantics live in the nested schema (webhook.url delivery behavior, intervalSignalLimit, checks) which the description never references, so it fails to compensate for the coverage gap.

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

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update a monitor' is a verbatim restatement of the tool name monitors-update; it names a verb and resource but adds no scope, no statement of what can be updated, and no differentiation from the many monitors-* siblings (update_action, pause, resume, trigger). Per the rubric this is the tautology case, which caps the score at 2.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus monitors-update_action, monitors-pause/resume, or monitors-create, and no mention of prerequisites or side effects. Usage must be inferred entirely from the tool name.

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

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