Skip to main content
Glama

BRAINIAC Environmental, Carbon & Water Intelligence

Build environmental evidence report

environmental-intelligence_evidence-report

Aggregate emission-factor, Scope 1–3, carbon-report, water, permit, and waste sections from caller-supplied operational records (and optional Carbon Intensity fetch). Price $0.08 USDC. POST /api/v1/environmental-intelligence/evidence-report. 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_evidence-report"
  }
}

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.3/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 does deliver real behavioral facts: price ($0.08 USDC), HTTP method/path, and the 402 failure mode where unpaid calls "do not run." It does not say whether the operation persists anything or is purely computational, nor what the delivered report looks like or how large it may be, which matters given no output schema.

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 compact sentences, front-loaded with what the tool produces before the commercial and transport details. The endpoint path and 402 note are load-bearing for a paid HTTP tool; there is little filler.

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 nesting, 0% schema coverage, no output schema, and no annotations, the definition is thin: it never explains how the five payload inputs (csv/json/text/file/files) relate, what the returned report contains, or how consistencyToleranceKg, waterAnomalyZ, and expiryWarningDays change results. An agent could not confidently assemble a correct call from this text alone.

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 0% across 17 nested parameters, so the description must compensate. It partially does by mapping report sections to parameter families (emission-factor→factors, Scope 1–3→activities/reports, water→waterRecords, permit→permits, waste→wasteManifests, Carbon Intensity→carbonIntensity), but leaves csv/json/text/file/files, asOf, expiryWarningDays, consistencyToleranceKg, and waterAnomalyZ entirely unexplained.

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?

Uses a specific verb ("Aggregate") and enumerates the exact sections produced: emission-factor, Scope 1–3, carbon-report, water, permit, waste. This implicitly distinguishes it from the single-domain siblings (scope-1/2/3 calculators, permit-expiry-check, water-anomaly-detect) as the composite report builder, though it never names an alternative outright.

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 phrase "caller-supplied operational records" signals this runs on data you provide rather than fetching live, and "optional Carbon Intensity fetch" marks the one external call. There is no explicit when-to-use vs when-to-use-a-sibling statement, and no prerequisites beyond the payment note.

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