Skip to main content
Glama

BRAINIAC Environmental, Carbon & Water Intelligence

Detect water consumption anomalies

environmental-intelligence_water-consumption-anomaly-detect

Detect anomalous water consumption using z-scores on caller-supplied facility water quantity series. Price $0.03 USDC. POST /api/v1/environmental-intelligence/water-consumption-anomaly-detect. Unpaid calls return 402 and do not run.

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": "environmental-intelligence_water-consumption-anomaly-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
factorsNo
permitsNo
reportsNo
suppliersNo
activitiesNo
waterRecordsNo
waterAnomalyZNo
wasteManifestsNo
carbonIntensityNo
expiryWarningDaysNo
consistencyToleranceKgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations present, the description does real work by disclosing the price ($0.03 USDC), the transport (POST plus path), and the failure mode ('Unpaid calls return 402 and do not run'). However, it says nothing about what the detection returns, how many records are needed for a meaningful z-score, or how waterAnomalyZ changes behavior.

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?

Three short sentences, no filler, with the core purpose front-loaded before pricing and endpoint details. The endpoint path is arguably redundant given the tool name, but everything else earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 17 optional parameters, deeply nested inputs, no annotations, and no output schema, the description is far too thin. An agent cannot tell which inputs are actually needed for a water anomaly run versus which belong to the broader environmental-intelligence payload, nor what shape of result comes back.

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

Parameters2/5

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

Schema description coverage is 0% across 17 parameters, several of them nested object arrays (waterRecords, activities, suppliers, files). The description only hints that the caller supplies a water quantity series, leaving asOf, waterAnomalyZ, csv/json/text vs file/files, and the unrelated emissions parameters entirely uninterpreted.

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?

States a specific verb and resource ('Detect anomalous water consumption') plus the method ('z-scores') and the input type ('caller-supplied facility water quantity series'). That is enough to distinguish it from the nearest sibling, water-intensity-calculate, without opening either schema, though the description never names an alternative explicitly.

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: the agent can infer this tool is for finding outliers in a facility water time series it already supplies. There is no statement of when to prefer it over siblings like water-intensity-calculate or permit-expiry-check, and no prerequisites beyond payment.

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