Skip to main content
Glama

BRAINIAC Environmental, Carbon & Water Intelligence

Check carbon report consistency

environmental-intelligence_carbon-report-consistency-check

Compare reported Scope 1–3 totals to summed scope values from caller-supplied reports and/or calculated activities. Flags inconsistent totals within tolerance. Price $0.04 USDC. POST /api/v1/environmental-intelligence/carbon-report-consistency-check. 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_carbon-report-consistency-check"
  }
}

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, the description carries the burden of behavioral disclosure. It usefully states the price ($0.04 USDC), the POST endpoint, and that unpaid calls return 402 and do not run, but it does not disclose side effects, read-only status, rate limits, or output 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?

The description is front-loaded and wastes little space: it states the comparison, the flagging behavior, pricing, endpoint, and payment failure behavior in four sentences. The endpoint path is somewhat redundant with the tool name, keeping it from a 5.

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 complex tool with 17 parameters, no annotations, no output schema, and 0% schema description coverage, the description is too thin. It explains the high-level check and payment requirement but leaves input formats, parameter roles, tolerance defaults, and return behavior largely undocumented.

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. It only loosely maps to a few inputs by mentioning 'reports', 'calculated activities', and 'tolerance'; the other 14 parameters, including files, factors, permits, suppliers, water records, waste manifests, and carbonIntensity, receive no explanation.

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 and resource: 'Compare reported Scope 1–3 totals to summed scope values'. It clearly identifies the consistency-check purpose, though it does not explicitly differentiate this tool from sibling calculation or validation tools by name.

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 by the comparison of reported totals against summed scope values from caller-supplied reports and/or calculated activities. However, it gives no explicit when-to-use/when-not-to-use guidance and names no alternative tool for related tasks.

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