Skip to main content
Glama

Microburbs Australian Property Data

State · Illicit drug consumption (wastewater)

states_health_drug_use
Read-onlyIdempotent

Estimated kilograms of methylamphetamine, cocaine, MDMA and heroin consumed each financial year from 2016-17 to 2024-25, for Australia and each state and territory, measured from sewage. Modelled estimates.

Coverage: Australia and all 8 states and territories; financial years 2016-17 to 2024-25. Current to 2025-06-30. Full description, field list and method: /v1/datasets/drug-use.

Price: 5¢ per call.

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": {
      "state": "<state>"
    },
    "name": "states_health_drug_use"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast period to include, same formats as `from`.
fromNoFirst period to include: 2020, 2020-Q3, 2020-07 or 2020-07-01.
stateYesState or territory abbreviation: nsw, vic, qld, sa, wa, tas, act or nt.
fieldsNoComma-separated subset of: meth_kg, cocaine_kg, mdma_kg, heroin_kg, total_kg. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: the figures are modelled estimates rather than raw measurements, currency is to 2025-06-30, and each call costs 5¢ — the cost signal in particular affects agent behavior. It does not describe response shape or result-size limits, which keeps it from a 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?

The measure and units come first, then a clearly delineated Coverage block with geography, time range and currency, then a documentation pointer and price. Nothing is padded. The standalone bolded '**Modelled estimates.**' sentence is a slightly awkward interruption in flow but the emphasis is arguably intentional for a statistical caveat.

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?

With no output schema, the description does the necessary work: it names the metric and units (kg), the substances, the time span, the geography and the modelling caveat. Combined with 100% schema coverage, an agent has enough to call it correctly. The residual gap is a mild scope inconsistency between claimed Australia-wide coverage and the state-only parameter, which could confuse an agent seeking national totals.

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%: `from`/`to` formats, the state abbreviations, and the comma-separated `fields` subset (meth_kg, cocaine_kg, mdma_kg, heroin_kg, total_kg) are all documented in the schema. The description adds nothing about parameter meaning beyond that, apart from noting a full field list exists at another endpoint. Baseline 3 applies when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and measure: estimated kilograms of methylamphetamine, cocaine, MDMA and heroin consumed per financial year, derived from sewage sampling, at state/territory granularity. That is far more informative than the title alone. It stops short of a 5 because it does not contrast itself with the sibling australia_health_drug_use, and it oddly claims coverage of 'Australia and all 8 states and territories' even though the required `state` parameter only offers abbreviations nsw–nt.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the tool for state-level wastewater drug-consumption figures over 2016-17 to 2024-25. There is no explicit when-to-use/when-not-to guidance and no routing to the national-level sibling for country-wide queries. The pointer to '/v1/datasets/drug-use' helps an agent find method detail, but that is documentation, not selection guidance.

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.

Resources