Skip to main content
Glama

Microburbs Australian Property Data

Australia · Illicit drug consumption (wastewater)

australia_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

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": "australia_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.
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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, yet the description still adds genuinely useful context: that the figures are modelled estimates rather than raw measurements, the data currency date (2025-06-30), and a stated price of 5¢ per call. The main omission is any note on refresh cadence or estimate uncertainty.

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 description is short, front-loaded with the measure and units, and uses a clear Coverage block plus a cost line. The financial-year range is stated twice (opening sentence and Coverage), which is minor redundancy but keeps each remaining line purposeful.

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 and all parameters optional, the description supplies the essentials: units (kg), substances, temporal and geographic scope, 'modelled estimates' caveat, and pricing. Only a brief note on what a default (no-parameter) call returns would make it fully self-sufficient.

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 schema already explains the from/to date formats and the field list, so the description does not need to repeat them. It adds only the pointer to /v1/datasets/drug-use for the full field list and method, which is marginal over the schema.

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 names a concrete measure (estimated kilograms consumed per financial year), the four substances, the geography and the wastewater-derived method, so an agent knows exactly what data comes back. It does not differentiate itself from the sibling states_health_drug_use, and since this tool claims to cover 'Australia and each state and territory' the split between the two is left ambiguous.

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 only implied through the stated coverage (national plus state/territory, FY2016-17 to 2024-25). There is no explicit 'use this when…' or 'use X instead for state-only breakdowns', so an agent must infer routing from sibling names alone.

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