Skip to main content
Glama

Node resources

cron_get_node
Read-onlyIdempotent

Retrieve live whole-host CPU and memory usage, optionally with recent history, to check overall host load and distinguish it from a single job's resource share.

Instructions

This node's live whole-host CPU/memory (optionally with the recent history). Use it to check host load; use cron_get_job_resources for one job's share.

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_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
historyNoAlso return the retained CPU and memory history that the dashboard's node chart shows (the last hour by default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.73
    • addedInput schema / properties / history / default
      Added value: +false
    • addedInput schema / properties / history / description
      Added value: +"Also return the retained CPU and memory history that the dashboard's node chart shows (the last hour by default)."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by clarifying that the sample is live and host-wide, and that history is opt-in rather than default. It does not cover failure modes (e.g. node unreachable) which keeps it below a 5.

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 short sentences: the return payload first, then routing guidance. Every clause earns its place with no preamble or restatement of the title.

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 simple, single-flag read tool with full annotation coverage, this is nearly complete — what it returns and when to pick it are both stated. The only minor gap is the absence of any hint about unavailable-node behavior, which is low-stakes here and not required for correct invocation.

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?

With a single parameter at 100% schema description coverage, the schema already fully documents the history flag, including its default and the one-hour retention window. The description only echoes that history is optional, adding no syntax or format detail beyond 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?

States precisely what is returned (live whole-host CPU/memory) with an optional history variant, and the scope word 'whole-host' distinguishes it from per-job metrics. An agent can tell it apart from cron_get_job_resources without inspecting either schema.

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?

Gives an explicit use case ('check host load') and names the alternative sibling with the condition that selects it ('for one job's share'). Nothing is left to inference.

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