Skip to main content
Glama

BRAINIAC Environmental, Carbon & Water Intelligence

Reconcile waste manifests

environmental-intelligence_waste-manifest-reconcile

Reconcile shipper and receiver waste manifest rows by manifest number, waste code, unit, and quantity. Price $0.04 USDC. POST /api/v1/environmental-intelligence/waste-manifest-reconcile. 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_waste-manifest-reconcile"
  }
}

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 behavior burden, and it does disclose real operational facts: cost ($0.04 USDC), transport (POST to a named endpoint), and paywall semantics (unpaid calls return 402 and do not run). It says nothing about what the reconciliation returns, how mismatches or tolerance thresholds are handled, or whether the operation mutates anything.

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 tight sentences, front-loaded with the substance (what is matched and on what keys) before logistics. The raw endpoint path is somewhat redundant with the tool name, but it is short and does not crowd out the core statement.

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 17-parameter, deeply nested tool with no annotations and no output schema, the description is thin: it does not describe the payload envelope (csv/json/text/file/files), explain how nested collections like factors or permits influence reconciliation, or indicate what the caller gets back. Only the pricing and paywall details are complete.

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, many of them nested arrays (wasteManifests, factors, permits, reports, suppliers, activities, waterRecords). The description only names the four matching fields inside wasteManifests and never explains csv/json/text/file vs files, asOf, expiryWarningDays, consistencyToleranceKg, or carbonIntensity, so the bulk of the input surface remains opaque.

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 gives a specific verb and resource ('Reconcile shipper and receiver waste manifest rows') and even names the join keys (manifest number, waste code, unit, quantity), which is far more precise than the title. It does not explicitly contrast with siblings such as permit-expiry-check, but the resource is distinct enough that confusion is unlikely.

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 stated prerequisites (e.g. that both shipper and receiver rows must exist), and no mention of what to do when data is incomplete. The only usage constraint given is payment-related, not task-related.

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