Skip to main content
Glama

Cluster view

cron_get_cluster
Read-onlyIdempotent

Inspect this node's cluster and leadership status to see peers, quorum, role, and live load, identify the leader, and confirm whether quorum holds.

Instructions

This node's cluster/leadership view (peers, quorum, role, live load). Returns enabled:false if no cluster is configured. Use it to see which node leads and whether quorum holds; use cron_get_fleet to compare each job's runs across nodes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavior beyond that by disclosing the returned fields and the enabled:false case when no cluster is configured, though it does not discuss freshness or error conditions.

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?

Two tight sentences front-load the resource and its contents, then add the no-cluster return behavior and sibling routing. No sentence is redundant.

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 zero-parameter read-only diagnostic tool with no output schema, the description gives enough context: what the view contains, what it means when no cluster exists, and when to use the fleet alternative. Nothing needed to invoke it correctly is missing.

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?

The tool has zero parameters, so there is nothing for the description to disambiguate. The schema coverage is complete and the baseline for a zero-parameter tool is appropriately met.

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 resource and view: this node's cluster/leadership state, including peers, quorum, role, and live load. It clearly distinguishes the tool from cron_get_fleet, which is framed as job-run comparison across nodes.

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 explicitly says to use this tool to see which node leads and whether quorum holds. It also names cron_get_fleet as the alternative for comparing each job's runs across nodes, giving a clear routing rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.