Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Change a monitor

uptime_update_monitor

Change what a monitor checks, how often, who is told, or pause and resume it. Give only what changes. Costs $0.001 per call; nothing if it fails.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "monitor_id": "<monitor_id>"
    },
    "name": "uptime_update_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoThe https:// page to check.
nameNoe.g. "Online shop".
pausedNo
publicNoShow it on the status page.
monitor_idYesThe monitor_id uptime_add_monitor returned.
expect_textNoText the page must contain to count as up, e.g. "Add to cart".
email_alertsNoAlso email the owner.
notify_channelsNoNotification channels (notify_add_channel) to alert.
interval_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds behavior the annotations cannot express: partial-update semantics (only send changed fields) and the cost model ($0.001 per call, free on failure). It stops short of saying what is returned or what happens on an invalid monitor_id.

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 capability, followed by the partial-update rule and the cost. No filler.

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?

With 9 parameters and no output schema, the description should ideally state what comes back after an update and any permission or validation behavior (e.g., failure on unknown monitor_id). It covers purpose, partial updates, and cost, but leaves the return contract and error behavior to inference.

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 78%, so most parameters are already documented individually. The description adds a useful conceptual grouping (checks/frequency/notifications/pause) that maps to url, expect_text, interval_minutes, notify_channels, email_alerts, and paused, but provides no new constraints or formats.

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 resource (monitor) and enumerates the changeable facets: what it checks, frequency, notification targets, and pause/resume. This clearly separates it from siblings uptime_add_monitor, uptime_get_monitor, and uptime_remove_monitor without needing their schemas.

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?

"Give only what changes" communicates partial-update semantics, which is real usage guidance. However, it never names alternatives (e.g., use uptime_get_monitor to read current config first, or uptime_remove_monitor to delete) and gives no when-not guidance.

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

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