Skip to main content
Glama
hoodsy

solarnetwork-mcp

by hoodsy

Most recent datum

get_latest
Read-only

Retrieve the most recent datum for each source of a SolarNetwork node, including watts and wattHours. Optionally specify a date to include older data.

Instructions

What is the most recent datum for each of a node's sources, and when was it recorded? Values are the device's own property map (e.g. watts, wattHours) passed through as-is — property names are the only unit hints; do not invent units. Sources silent for ~90 days are omitted unless you pass sinceDate to look further back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesSolarNetwork node ID (public demo node: 108)
sinceDateNoUTC date to look back to; without it the API only considers the last ~90 days
sourceIdsNoSource IDs to include; omit for all
Behavior5/5

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

Adds substantial context beyond annotations: values are pass-through property maps with unit hints from names, silent source behavior, and sinceDate override. No contradiction with readOnlyHint or openWorldHint.

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 efficient sentences with front-loaded purpose, no redundancy.

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?

Sufficiently explains return format and key constraints, though lacks mention of pagination or response structure. Adequate given no output schema.

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 descriptions cover all 3 parameters (100% coverage). Description adds behavioral context but minimal extra meaning for individual parameters 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?

Description clearly states it returns the most recent datum per source with timestamp, and distinguishes from siblings like query_datum (historical) and get_meter_reading (aggregate).

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 explains when to use sinceDate to bypass the ~90-day silent source filter, but does not mention alternative tools or when not to use this tool.

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/hoodsy/solarnetwork-mcp'

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