Skip to main content
Glama

NEM Explorer (ScadaMiner)

get_table_schema

Read-onlyIdempotent

Get the full column schema for a specific table, including AEMO-published metadata: per-column description, units, valid enum values, primary-key flags, and available_from (the MMSDM release month a column was added — present only for late-added columns like 1-second FCAS RRPs; don't query those for earlier dates). Also returns table-level documentation (description, source/volume notes, package id) and a curated selector block carrying the hard-learnt caveats, grain, join_keys, related_tables, and question_tags — read the caveats before composing SQL. Pass the exact object_name from list_tables. Use this once you've picked a table; for cross-table column lookup use search_columns.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table_name": "<table_name>"
    },
    "name": "get_table_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
table_nameYesFully-qualified table name, e.g. `consolidated.dispatch__dispatch__unit_solution` or `semantic.duid_fuel_type`. Use the exact `object_name` from `list_tables`.
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.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds real substance: the shape of the returned payload, the semantics of available_from, and the instruction to read the caveats block before composing SQL. It stops short of describing error behavior, size limits, or how the selector block is structured, which keeps it at 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then layered detail, with zero filler sentences. The second sentence is long and packs many quoted field names, which makes it slightly dense to scan, but every clause carries distinct information.

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?

There is no output schema, so the description must carry return-value information, and it does so thoroughly: column-level fields, table-level documentation, and the curated selector block with its caveats/grain/join_keys contents. Combined with the usage routing and the available_from caution, an agent has everything needed 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?

Schema coverage is 100% and both parameters are documented there, so the baseline of 3 applies. The description reinforces the key constraint on table_name (exact object_name from list_tables) but adds nothing about the optional question_id attribution parameter beyond what the schema already says.

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?

Opens with a specific verb+resource ("Get the full column schema for a specific table") and enumerates exactly what is returned: per-column description, units, enum values, primary-key flags, available_from, table-level docs, and the selector block. It explicitly disambiguates from siblings: list_tables is the source of the name, search_columns is for cross-table lookup.

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?

States the precondition clearly ("Use this once you've picked a table"), names the alternative for the adjacent need ("for cross-table column lookup use search_columns"), and tells the agent to pass the exact object_name from list_tables. It also gives a when-not-to-use rule for late-added columns: don't query those for dates before available_from.

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.