Skip to main content
Glama

NEM Explorer (ScadaMiner)

get_data_freshness

Read-onlyIdempotent

Return the warehouse's latest 5-minute SETTLEMENTDATE (the most recent data point present in dispatch-side tables) plus the current NEM time. Use this to bound date ranges in queries — anything past latest_settlementdate returns no rows. NEM time is Australia/Brisbane: UTC+10 with no daylight saving. Reach for this FIRST for any "how fresh / how current / latest date" question — never hand-roll max(SETTLEMENTDATE) over a consolidated table, which scans the whole table and is rejected by a per-query resource cap. For per-table availability bounds (the earliest date, or the range a specific table covers) use list_tables (data_available_from / data_available_to) — also scan-free.

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

Input Schema

NameRequiredDescriptionDefault
question_idNoOptional UUID returned by an earlier `start_question` call. When provided, this tool call is attributed to that question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds context those fields cannot carry: the data-point semantics (5-minute resolution), the timezone rule (Australia/Brisbane, UTC+10, no DST), the consequence of querying past latest_settlementdate (no rows), and a per-query resource cap constraint that affects how the tool must be used.

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 return content is front-loaded, followed by the bounding caveat, the timezone fact, and the routing/anti-pattern guidance. Every sentence carries new operational information; nothing is restated from the title or annotations.

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

Completeness5/5

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

No output schema exists, so the description takes on the burden of explaining return values, which it does (latest settlement date plus NEM time). For a zero-required-parameter read tool, it also supplies the edge cases (past-latest returns nothing, timezone, scan cap) an agent needs to call it correctly.

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?

There is only one optional parameter (question_id) and schema description coverage is 100%, so the schema already fully documents it. The description adds nothing about that parameter, leaving this at the baseline for fully-covered schemas.

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 a specific verb and resource: returns the latest 5-minute SETTLEMENTDATE present in dispatch-side tables plus the current NEM time. It explicitly contrasts with list_tables for per-table availability bounds, so an agent can separate the two without opening 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 explicit routing: 'Reach for this FIRST' for freshness/latest-date questions, an explicit prohibition against hand-rolling max(SETTLEMENTDATE) with the reason (full-table scan, resource cap), and names list_tables for the adjacent use case. Both when-to-use and when-not-to-use are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.