Skip to main content
Glama

get_temperature_history

Read-onlyIdempotent

Retrieve cached temperature history for every heater and sensor to check whether a heater is tracking its target or a thermal runaway is developing.

Instructions

Moonraker's cached temperature history (roughly the last 20 minutes, 1 Hz) for every heater and sensor: temperatures, targets, and power. Use this to judge whether a heater is tracking its target or a thermal runaway is developing.

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

Input Schema

NameRequiredDescriptionDefault
last_nNo
sensorNo
include_monitorsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description adds the genuinely useful behavioral facts of a bounded cache (~last 20 minutes at 1 Hz) and the data payload per sample. It stops short of saying what happens when more data is requested than the cache holds, or what an invalid sensor name yields.

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 tightly written sentences with no filler. Scope and retention window come first, and the diagnostic use case follows, which is the correct front-loading for this tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is unnecessary, and the description covers retention, sample rate, payload contents, and intent. However, with zero schema description coverage on three optional parameters, an agent still cannot confidently choose values for last_n, sensor, or include_monitors from this text alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all three parameters, so the description must carry the burden and largely does not. It never explains whether 'last_n' is a sample count or a time window, what format 'sensor' expects, or what 'include_monitors' adds; only the ~20 minute/1 Hz note indirectly bounds last_n, and 'every heater and sensor' only loosely implies filtering.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and its scope: cached temperature history across every heater and sensor, with temperatures, targets, and power. The word 'history' plus the ~20 minute window implicitly separates it from the current-value sibling get_temperatures, but that sibling is never named, so the differentiation is left to inference.

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?

Explicitly tells the agent when this is the right tool: 'Use this to judge whether a heater is tracking its target or a thermal runaway is developing,' which is a concrete diagnostic scenario. It gives no exclusions or pointers to alternatives such as get_temperatures or wait_for_temperature, so the agent must infer that current-state checks belong elsewhere.

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

Deploy Server

Other Tools