Skip to main content
Glama

Add a site to monitoring

add_site
Idempotent

Start monitoring a website: it is scanned now, then re-scanned on your plan schedule, with uptime checks and email alerts.

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": {
      "url": "<url>"
    },
    "name": "add_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesWebsite URL or domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as a non-destructive, idempotent mutation with open-world effects. The description adds useful behavioral context beyond those hints: the site is scanned immediately, re-scanned on the plan schedule, and produces uptime checks and email alerts. It stops short of explaining duplicate-URL behavior or what the response contains.

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?

A single, front-loaded sentence with no wasted words. Each clause (immediate scan, scheduled re-scan, uptime checks, alerts) contributes useful information.

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 simple one-parameter mutation tool with full schema coverage and safety annotations, the description explains what happens on invocation. It lacks only edge-case behavior such as how duplicate URLs are treated and what is returned, which is a minor gap given the annotations and 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?

There is one parameter, and schema description coverage is 100% ('Website URL or domain' with min/max length). The description adds no format guidance beyond the schema, so the 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 ('Start monitoring a website') and adds concrete scope: immediate scan, scheduled re-scans, uptime checks, email alerts. It does not explicitly differentiate itself from siblings like scan_site or recheck_site, so an agent must infer that this is the persistent-monitoring entry point rather than a one-off scan.

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 is only implied: adding a site is how you begin monitoring it. The description does not say when to choose this over scan_site (one-off scan) or recheck_site, nor does it state prerequisites such as plan limits or duplicate handling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources