Skip to main content
Glama

Set cluster security report schedule

set_cluster_security_report_schedule
Destructive

Store the cluster's scheduled security report: how often it is emailed (weekly or monthly), to whom (up to 20 addresses) and whether sending is enabled. Enabled requires at least one recipient; disabled keeps the configuration without sending. Replaces the whole schedule. Reversible: store it again or disable it.

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": {
      "frequency": "<frequency>",
      "recipients": "<recipients>"
    },
    "name": "set_cluster_security_report_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNotrue to send on schedule (the default when omitted, like the REST body), false to store the configuration paused.
frequencyYesweekly or monthly.
cluster_idNoCluster id (UUID). Optional when the conversation is bound to a cluster.
recipientsYesEmail addresses that receive the report, at most 20; at least one when enabled is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond destructiveHint, it discloses that the operation replaces the entire schedule and is reversible by storing again or disabling it. It also clarifies that disabled preserves the configuration without sending and that enabled needs at least one recipient, which is useful mutation context. It stops short of detailing permissions or failure modes.

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 sentences are front-loaded with the core action and key constraints; every clause carries useful information. 'Replaces the whole schedule' and the reversibility note are especially important for a destructive setter and are stated without padding.

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 mutation tool with no output schema, the description covers frequency options, recipient limit, enabled semantics, replacement behavior, and reversibility. The optional cluster_id and default enabled are left to the schema, which is acceptable at full coverage. Nothing critical for correct invocation is missing.

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 100%, so all four parameters are already documented, including default enabled behavior and the recipient maximum. The description reinforces the enabled/recipients relationship but does not add format, validation, or constraint details beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb ('Store') and resource ('cluster's scheduled security report'), and it enumerates the fields being set (frequency, recipients, enabled). This clearly separates it from reading the schedule or triggering an immediate send, even without naming those siblings.

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 explains the operational choice between enabled and disabled schedules, and notes this call replaces the whole schedule rather than patching it. It does not explicitly name alternatives such as get or send-now, so an agent must infer that this is the configuration tool, not the inspection or immediate-send tool.

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.