Skip to main content
Glama
gopisrikrishna

solarnetwork

by gopisrikrishna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List known public nodes

list_public_nodes

Find public SolarNetwork nodes without credentials by scanning node IDs 1-5000. Filter to live nodes or by timezone to locate active solar sites.

Instructions

List SolarNetwork nodes known to be readable without credentials, from a catalogue built by scanning node IDs 1-5000. Use this first when you do not have a node ID in hand, since there is no public endpoint that enumerates nodes. Filter to live nodes to avoid ones that stopped reporting years ago.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
liveOnlyNoOnly nodes with data since 2026-08-01
timeZoneNoFilter by IANA timezone substring, e.g. 'America'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that nodes are readable without credentials, that the catalogue comes from scanning IDs 1-5000, and that dead nodes should be filtered to avoid stale data. It does not mention output format or rate limits, but these are less critical for a simple list operation.

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 sentences: purpose, usage guidance, and filtering tip. Every sentence earns its place, with the core behavior front-loaded and no wasted words.

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?

Given two optional parameters and no output schema, the description adequately covers purpose, scope, and usage. It could mention what fields are returned or how results are ordered, but an agent can invoke the tool correctly with the information provided.

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 description coverage is 100%, so the baseline is 3. The description adds a rationale for the liveOnly parameter ('avoid ones that stopped reporting years ago') but does not add new meaning for either parameter beyond what the schema already provides.

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 clearly states the tool lists SolarNetwork nodes that are publicly readable, sourced from a catalogue built by scanning node IDs 1-5000. This is a specific verb+resource and differentiates it from sibling tools that operate on known nodes or sources.

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?

The description explicitly instructs to use this tool first when no node ID is available, and explains why (no public endpoint that enumerates nodes). It also advises filtering to live nodes to avoid stale entries, but it does not name alternative tools for when a node ID is already known.

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