Skip to main content
Glama

Send cluster security report now

send_cluster_security_report_now
Destructive

Email the cluster's security report to its scheduled recipients within the next minute instead of waiting for the next due date. Refuses when no schedule is configured yet (set_cluster_security_report_schedule first). Sends real email to the stored recipients.

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": "send_cluster_security_report_now"
  }
}

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.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false, and idempotentHint=false; the description adds genuine context beyond that — that real email goes to stored recipients and that the call is refused without a configured schedule. It stops short of stating what a repeat invocation does (i.e., whether a second send duplicates the email) and does not describe the response or any rate limits.

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 short sentences, front-loaded with the action and its timing semantics, followed by the failure precondition and the side-effect warning. No filler or repeated 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 single-optional-parameter action tool with no output schema, the description covers purpose, precondition, and the side effect, which is nearly everything an agent needs. The one remaining gap is what a successful call returns or confirms, which is left implicit.

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%, so cluster_id's UUID format and its optionality when the conversation is bound to a cluster are already documented in the schema. The description adds no cluster-targeting detail, so the baseline of 3 applies.

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 states a specific verb and resource ("Email the cluster's security report to its scheduled recipients") and immediately distinguishes the scope from waiting for the next due date. It is clearly separable from read-only siblings like get_security_reports and from the prerequisite set_cluster_security_report_schedule.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance ("within the next minute instead of waiting for the next due date") and an explicit when-not/prerequisite: it refuses when no schedule exists and instructs the agent to call set_cluster_security_report_schedule first. The alternative is named directly.

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.