Skip to main content
Glama

BRAINIAC Environmental, Carbon & Water Intelligence

Calculate water intensity

environmental-intelligence_water-intensity-calculate

Calculate water intensity (m³ per denominator unit) from caller-supplied water quantities and production/occupancy denominators. Price $0.03 USDC. POST /api/v1/environmental-intelligence/water-intensity-calculate. 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-intensity-calculate"
  }
}

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

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: a $0.03 USDC price, the endpoint path, and that unpaid calls return 402 and do not execute. However, it says nothing about how partial or malformed input is handled, what validation occurs across the many record arrays, or what the response contains.

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 purpose statement is front-loaded and the three sentences are tight, with price and endpoint stated compactly. The endpoint path restates the tool name and is slightly redundant, but nothing is bloated.

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 parameters, deep nested objects, no output schema, and no annotations, this description is far too thin. An agent cannot determine which input channel to use (files vs csv vs json), what the required data shape is for waterRecords, or what the result looks like.

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, so the description must compensate and largely does not. It only gestures at the water quantities and denominators conceptually; the file/csv/json/text payloads, factors, permits, reports, suppliers, activities, wasteManifests, anomaly z-score, and tolerance parameters are left entirely undocumented.

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 uses a specific verb ('Calculate') and resource ('water intensity'), and defines the output unit (m³ per denominator unit) plus the inputs it consumes (water quantities and production/occupancy denominators). It does not name a sibling to differentiate from, but the purpose is unambiguous on its own.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no routing to alternatives such as the water-consumption anomaly detector. The only conditional statement is about payment ('unpaid calls return 402'), which is billing behavior rather than invocation 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