Skip to main content
Glama

BRAINIAC Environmental, Carbon & Water Intelligence

Validate Scope 3 supplier data

environmental-intelligence_scope-3-supplier-data-validate

Validate caller-supplied Scope 3 supplier emission rows for identity, period, quantity, and factor provenance. Recalculates when activity quantity and a factor are available. Price $0.04 USDC. POST /api/v1/environmental-intelligence/scope-3-supplier-data-validate. 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_scope-3-supplier-data-validate"
  }
}

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.4/5.0
Behavior4/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 real work: it discloses the $0.04 USDC price, the POST endpoint, that unpaid calls return 402 and do not run, and that recalculation happens when activity quantity plus a factor are present. It stops short of saying whether validation is read-only, what a failed validation returns, or how partial failures are reported.

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?

Four short sentences, front-loaded with the purpose, then the recalculation condition, then the commercial and transport facts. Nothing is padded, though the raw endpoint path is the least valuable sentence for an agent deciding whether to call.

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

Completeness3/5

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

For a 17-parameter, deeply nested tool with no annotations and no output schema, the description covers purpose, pricing, and one behavioral rule but not the shape of a validation result or the role of the many non-supplier payload sections. It is adequate to decide whether to call, not to call it correctly.

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 top-level parameters, so the description must compensate and only partly does. It maps meaning onto a few fields (activity quantity, factor provenance, period, identity) but leaves csv, json, text, file, files, permits, reports, activities, waterRecords, wasteManifests, carbonIntensity, expiryWarningDays, consistencyToleranceKg, and asOf 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?

States a specific verb (validate) and a specific resource (caller-supplied Scope 3 supplier emission rows), and enumerates the checks performed: identity, period, quantity, and factor provenance. That is enough to separate it from the calculate and consistency-check siblings, though it 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 by the purpose: an agent can infer this is the tool for checking supplier rows before reporting. There is no explicit when-to-use versus environmental-intelligence_carbon-report-consistency-check or the scope-1/scope-2 calculate tools, and no stated preconditions.

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