Skip to main content
Glama

NEM Explorer (ScadaMiner)

search_columns

Read-onlyIdempotent

Search column documentation by words, in any order and ignoring case, across column names, column descriptions and AEMO table names. Use this when you know what you want to measure but not which table holds it (e.g. 'marginal value', 'loss factor', 'intervention', 'RRP'). Spaces and hyphens also match underscored or run-together names: 'local price adjustment' finds LOCAL_PRICE_ADJUSTMENT and 'marginal value' finds MARGINALVALUE. Hits contain every word, best name matches first; if no column has every word, the closest partial matches come back with matched_all_terms=false. Each hit lists the AEMO source table, the column name + description + units + valid values, and the consolidated.* views that expose the column — pick one of those for your SQL. The docs cover AEMO's whole data model, including tables the warehouse does not hold: those hits carry in_warehouse=false and a not_in_warehouse_reason (participant-private, retired by AEMO, not yet published by AEMO, or not ingested), rank after warehouse hits, and cannot be queried.

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": {
      "query": "<query>"
    },
    "name": "search_columns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of hits to return. Defaults to 25 — enough to compare candidates without blowing the context window.
queryYesWords to find in column names, column descriptions and AEMO table names, in any order and ignoring case (e.g. "MARGINALVALUE", "intervention", "loss factor", "local price adjustment"). Spaces and hyphens also match underscored or run-together column names, so "marginal value" finds MARGINALVALUE.
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
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add matching behavior—and it does extensively: word-order/case insensitivity, underscore/hyphen normalization, all-terms-required ranking, the matched_all_terms=false fallback, and the in_warehouse/not_in_warehouse_reason fields with the reasons enumerated. It even discloses that out-of-warehouse hits rank lower and cannot be queried.

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 purpose and usage, then behavior, then return shape—a logical progression. It is on the long side and the separator-matching rule is duplicated between description and schema, which is minor waste but not bloat.

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 describe return values, and it fully does: per-hit contents (source table, name, description, units, valid values, consolidated views) plus the partial-match and in_warehouse flags. Nothing needed to interpret results is missing.

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 the query parameter's schema description already restates the word-order, case, and separator-matching rules nearly verbatim, so the description adds little parameter-level meaning. The limit and question_id parameters are left entirely to the schema. Baseline 3 is appropriate.

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 ('Search column documentation') plus exact search scope (column names, column descriptions, AEMO table names), which cleanly separates it from search_entities and get_table_schema. An agent immediately knows this is a discovery tool over column metadata.

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 frames the use case: 'Use this when you know what you want to measure but not which table holds it,' reinforced with concrete example queries. It also tells the agent what to do next ('pick one of those for your SQL'), but never names a sibling alternative or a when-not-to-use condition.

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.