Skip to main content
Glama

Add an endpoint check

add_endpoint

Monitor a specific URL on one of your verified sites (for example an API health route, login or checkout page) with a GET or HEAD request on a schedule. The domain must be verified first, and the URL must not include a query string. Optionally require an exact HTTP status, a text snippet in the response, and a maximum response time. You get an email alert when it fails twice in a row and when it recovers. Wardzo never submits forms or sends request bodies.

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

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL on that site, or a path like "/api/health"
siteYesSite id, domain or URL of one of your monitored sites
max_msNoFail if the response takes longer than this many milliseconds
methodNoHTTP method (default GET)
expect_statusNoExact expected HTTP status (default: any 2xx or 3xx)
expect_keywordNoText that must appear in the response body (GET only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say it is a non-destructive, non-idempotent, open-world write; the description adds real behavioral context: it runs on a schedule, alerts by email after two consecutive failures and on recovery, and never submits forms or request bodies. That last point is a meaningful safety disclosure an agent could not infer from the annotations.

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?

Four sentences, front-loaded with what is created and under what constraints, then optional checks, then alerting behavior, then the safety guarantee. No filler and no repetition of the title.

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?

With six fully described parameters, annotations, and no output schema, the description covers prerequisites, allowed methods, validation rules, and alerting. It does not say what the call returns (for example an endpoint identifier) or what the polling interval defaults to, which would matter for a follow-up list_endpoints call.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not: the URL may be a path relative to the site, the method is limited to GET/HEAD, and the no-query-string rule constrains the url parameter. The optional status, snippet, and response-time checks map onto expect_status, expect_keyword, and max_ms without adding much beyond them.

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 concrete verb and resource: monitor a specific URL on one of your verified sites with a GET or HEAD request on a schedule. The scope constraints (verified domain, no query string) separate it cleanly from add_site and from list_endpoints/remove_endpoint in the sibling set.

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

Usage Guidelines4/5

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

Gives clear preconditions (domain must be verified first, URL must not carry a query string) and describes the optional checks that select the extra parameters. It never names a sibling alternative or says when not to use it, so it stops short of a 5.

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