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. 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"
-]
  2. 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"
+]
  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"
-]New value: +[
+  "job_posted",
+  "social_posted",
+  "funding_raised",
+  "investment_made",
+  "ipo_announced",
+  "ipo_stage_changed",
+  "repo_engaged"
+]
  4. Added

TDQS

C2.4/5.0
Behavior2/5

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

The description adds no behavioral context beyond what the annotations already convey. Annotations state readOnlyHint=false (mutation) and destructiveHint=false, and 'Update' is consistent with that, but nothing is disclosed about idempotency, partial vs. full replacement, permission requirements, or side effects on downstream signals. With annotations present, the description could add value but does not.

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?

The description is a single generic sentence, which is under-specification rather than conciseness for a tool with deeply nested parameters and multiple conditional fields. It front-loads nothing useful and fails to earn its place by conveying any actionable information.

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

Completeness1/5

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

Given the complexity of the input schema (nested objects, multiple enums, conditional fields) and the absence of an output schema, the one-line description is grossly insufficient. An agent cannot determine what fields are updatable, how the request body interacts with existing monitor settings, or what the response looks like. This is completely inadequate for safe invocation.

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?

The description contains zero parameter information. With schema description coverage at 50%, the schema partially documents nested fields, but the description does nothing to compensate for the undocumented half or clarify parameter behavior. An agent gets no help from the description in understanding monitorId or __requestBody beyond their raw schema.

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?

The description states a specific verb (Update) and resource (a monitor), and the tool name mirrors this, distinguishing it from sibling operations like monitors-create, monitors-delete, and monitors-pause. However, it does not describe what aspects of a monitor can be updated (e.g., name, checks, webhook, schedule), so it is clear but not fully differentiated from other update tools like monitors-update_action.

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?

No usage guidance is provided. The description does not say when to use this tool versus alternatives, when not to use it, or any prerequisites. An agent must infer usage solely from the name and schema.

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