Skip to main content
Glama

Get cluster security report schedule

get_cluster_security_report_schedule
Read-only

The cluster's scheduled security report: whether one is configured, its frequency (weekly or monthly), the email recipients, whether it is enabled, when it was last sent and when it is next due. Read-only. Pair with set_cluster_security_report_schedule to change it and send_cluster_security_report_now to deliver one immediately.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cluster_security_report_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoCluster id (UUID). Optional when the conversation is bound to a cluster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The readOnlyHint=true annotation is confirmed rather than contradicted, and the description adds real behavioral context: it discloses the returned state fields including last-sent and next-due timestamps. It doesn't cover edge behavior such as what is returned when no schedule exists or any permission prerequisites, so it stops short of full disclosure.

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?

Two sentences, front-loaded with the resource and its contents, followed by routing guidance. The field enumeration is dense but earns its place because no output schema exists; nothing is redundant.

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 one-optional-parameter read tool with no output schema, the description substitutes well by listing the fields an agent will receive. The only gap is the absence of stated error/empty-state behavior and permission requirements.

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 description coverage is 100% and the single cluster_id parameter is already documented as an optional UUID when the conversation is bound to a cluster. The description adds no additional parameter meaning beyond that, which is the expected baseline when the schema does the work.

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 resource (the cluster's scheduled security report) and enumerates exactly what is retrieved: configured-or-not, frequency (weekly/monthly), recipients, enabled state, last sent, next due. This clearly separates it from set_cluster_security_report_schedule and send_cluster_security_report_now, which are read/write and action 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 explicitly routes the agent: pair with set_cluster_security_report_schedule to change the schedule and send_cluster_security_report_now to deliver immediately. That is clear alternative guidance, though it stops short of stating when-not to use this tool (e.g., whether to prefer a broader security overview tool for cross-cluster questions).

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.