Skip to main content
Glama

NEM Explorer (ScadaMiner)

get_concept

Read-onlyIdempotent

Read the authoritative explainer for an AEMO market mechanism before you describe how or why it works. Available topics: fpp, four_second_data, settlements, mlf, forecasts, fcas, constraints, over_constrained_dispatch, operating_margins, interconnectors, battery, curtailment, market_notices, bidding, demand, topology, outages, revenue, sra, vwap, price_setting, market_price_cap, market_price_floor, cumulative_price_threshold, multi_metric, participant_ownership, market_power. Call with an unknown topic to get the current list back. Each guide gives the precise terms and mechanics, the tables/columns that matter, how to aggregate, common pitfalls, and typical value ranges. Do NOT explain a mechanism's mechanics from your own knowledge — the plausible phrasing is often subtly wrong; ground the explanation in this guide or say you can't confirm it.

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": {
      "topic": "<topic>"
    },
    "name": "get_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesMechanism topic to explain, e.g. `fpp`, `causer-pays`. Call with an unknown topic to get the list of available topics back.
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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral value beyond that: it discloses what each guide contains (precise terms and mechanics, relevant tables/columns, aggregation guidance, pitfalls, typical value ranges) and defines the unknown-topic error path. It does not mention latency or caching, which are minor here.

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?

The directive is front-loaded, and the long topic list is doing real work as a substitute for a missing enum. Every sentence contributes, though the 27-item inline list is dense and pushes the prescriptive guardrail ('do not explain from your own knowledge') to the end where it is easiest to skim past.

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?

With only two parameters, no output schema, and a closed-world read-only profile, the description supplies everything an agent needs: when to call, what the payload contains, how to recover from a bad topic, and how strictly to rely on the returned content. No material gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by enumerating 27 valid topic values in place of an enum and by explaining the sentinel behavior of an unknown topic. That said, there is a mild mismatch: the text names 'four_second_data' while the schema example uses 'causer-pays'-style hyphenation, so the exact string format remains slightly ambiguous.

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 ('Read the authoritative explainer for an AEMO market mechanism') and enumerates the exact topic domain it covers. An agent can immediately distinguish this from siblings like get_table_schema or get_dashboard_guide, which serve different reference needs.

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 an explicit trigger ('before you describe how or why it works'), an explicit prohibition ('Do NOT explain a mechanism's mechanics from your own knowledge'), a fallback for a failed lookup ('call with an unknown topic to get the current list'), and an alternative behavior when confirmation isn't possible ('say you can't confirm it'). This is close to a complete decision rule.

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.