Skip to main content
Glama

Turn outage emails on or off

setSiteCheckEmails
Idempotent

Turn one owned app’s outage emails on or off: the “isn’t answering” email Tofu sends its owner when two checks in a row fail, and the “answering again” email after it. Checks keep running either way, and their recorded results remain available. Requires confirmed: true, representing the human’s agreement to this exact change for this exact projectId. Turning emails off suppresses the owner’s outage notifications. Turning them back on applies from the next outage: one that opened while they were off is not emailed. Returns the app’s recorded visitor-check and email-notification state.

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": {
      "projectId": "<projectId>",
      "enabled": "<enabled>",
      "confirmed": "<confirmed>"
    },
    "name": "setSiteCheckEmails"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
confirmedYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
stateYes
uptimeYes
addressYes
messageYes
availableYes
lastCheckYes
projectIdYes
openIncidentYes
emailsEnabledYes
retentionDaysYes
recentIncidentsYes
checkEveryMinutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare non-read-only, idempotent, non-destructive; the description adds the substantive behavior an agent needs: the confirmation gate semantics, that disabling suppresses owner notifications, and the non-retroactive rule that emails re-enabled mid-outage will not fire for that outage. That last detail is exactly the kind of edge case annotations cannot express.

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

Conciseness4/5

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

The critical scope and confirmation requirement are front-loaded, and most sentences carry distinct information. There is mild redundancy between the opening sentence and 'Turning emails off suppresses the owner's outage notifications,' which restates the same effect.

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

Completeness5/5

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

For a three-parameter mutation with an output schema, the description covers the confirmation prerequisite, the state-change semantics, the non-retroactive edge case, and the returned state. Nothing an agent needs to invoke it correctly is missing, and return-value detail is appropriately deferred to the output schema.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the burden, and it does: it explains that `confirmed: true` represents a human's agreement to this exact change for this exact projectId, and it defines the semantics of `enabled` (suppression on/off, next-outage-only re-enable). Only `projectId`'s UUID format is left to the schema, which is reasonable since the format is self-documenting in the schema.

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?

The description names a specific verb and resource (turn one owned app's outage emails on or off) and immediately enumerates the two email types affected. It also bounds scope to a single owned app, so an agent can tell it apart from sibling site tools like siteChecks or siteAnalytics without opening a schema.

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?

It clarifies that checks keep running and results remain available when emails are off, which implicitly routes result-reading to the check tools rather than this one. It does not explicitly name an alternative tool or state exclusions, so it falls short of full when/when-not guidance.

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