Skip to main content
Glama
fredriksknese

mcp-openmediavault

get_cpu_temp

Monitor CPU temperature readings on OpenMediaVault NAS systems to track hardware health and prevent overheating issues.

Instructions

Get CPU temperature readings from OpenMediaVault

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'get_cpu_temp' tool that executes an RPC call to 'CpuTemp.getStats' and returns the CPU temperature readings as JSON. Handles errors and returns appropriate error messages.
    async () => {
      try {
        const result = await client.rpc("CpuTemp", "getStats", {});
        return toolResult(JSON.stringify(result, null, 2));
      } catch (error) {
        return toolResult(`Error fetching CPU temperature: ${error}`, true);
      }
    },
  • Tool registration for 'get_cpu_temp' using server.tool() method. Defines the tool name, description, empty input schema (no parameters), and the handler function.
    server.tool(
      "get_cpu_temp",
      "Get CPU temperature readings from OpenMediaVault",
      {},
      async () => {
        try {
          const result = await client.rpc("CpuTemp", "getStats", {});
          return toolResult(JSON.stringify(result, null, 2));
        } catch (error) {
          return toolResult(`Error fetching CPU temperature: ${error}`, true);
        }
      },
    );
  • Helper function that formats tool results into the expected MCP response format with content array and optional error flag.
    function toolResult(text: string, isError = false) {
      return { content: [{ type: "text" as const, text }], isError };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool reads CPU temperature but doesn't disclose behavioral aspects like whether it's a real-time snapshot or cached data, potential rate limits, authentication requirements, or error conditions. This is inadequate for a tool with zero annotation coverage.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple read operation, the description is incomplete. It doesn't explain what the output looks like (e.g., temperature units, format, or possible values), potential errors, or system dependencies, leaving significant gaps for an AI agent to use it effectively.

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 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it also doesn't compensate for any gaps since there are none. Baseline 4 is given as it meets minimal requirements without issues.

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?

The description clearly states the action ('Get') and resource ('CPU temperature readings from OpenMediaVault'), making the tool's purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_system_stats' or 'get_system_info' that might also provide temperature data, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_system_stats' and 'get_system_info' that might include temperature readings, there's no indication of whether this tool is more specific, real-time, or comprehensive, leaving usage context ambiguous.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fredriksknese/mcp-openmediavault'

If you have feedback or need assistance with the MCP directory API, please join our Discord server