Loading ToolBench
Progressive exergy, emissions, public-health screening, and economic analysis with transparent defaults.
Server has 23 tools with consistent naming (verb_noun pattern) and descriptions present for all. However, critical gaps exist: most tools accept generic 'inputs' object with no documented schema, making it impossible for LLMs to understand what fields are valid. Parameter descriptions are minimal (10-30 chars typical). Output schemas are undocumented. Error handling exists but lacks recovery guidance. Tool composition is reasonable but parameter documentation is weak.
Account for mass, composition, and explicitly supplied chemical exergy.
Account for energy and exergy across arbitrary connected components.
Aggregate chronological system records supplied as interval quantities.
Run an integrated process exergy, impact, opportunity, and economic assessment.
Assess a carrier, service, or technology with progressive-fidelity exergy accounting.
List workflows, input contracts, output schemas, and safety behavior.
Describe one workflow's accepted inputs, defaults, and outputs.
14 tools accept generic 'inputs' object parameter with no documented schema. LLMs cannot determine valid fields, types, or constraints. This violates the constrained-input pattern and forces agents to guess or call describe_workflow first.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields. Violates response-shaper pattern.
Parameter descriptions are minimal (10-30 chars). E.g., 'The name of the workflow to describe' lacks context on format, length, or valid values. Descriptions should be 50-200 chars with constraints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Apply sourced EPA regional ranges for monetized outdoor-air health benefits.
Estimate process energy from a sourced mass-normalized pack prior.
Estimate energy output without silently assuming an exergy factor.
Calculate project cash flow, payback, levelized costs, and abatement economics.
Evaluate a registered explicit-performance technology model.
Execute a recipe and write only the explicitly requested report paths.
List bundled carrier, service, technology, or reference profiles.
Infer or apply a mapping and normalize in-memory industrial records.
List opt-in public-data connectors, local adapters, and source terms.
List sourced EPA regional benefit ranges and unavailable combinations.
Run any stable exergy-imperative recipe in execute, dry-run, or validate-only mode.
Screen greenhouse gases and pollutant inventories with health context.
Find applicable workflows, profiles, components, packs, and schemas.
Show which pack technologies have sourced defaults.
List bundled data-only domain packs and their default policy.
Validate an inline, bundled, or explicitly named local technology pack.
Error handling returns error_response() but source code snippet is incomplete. Cannot verify if errors include recovery guidance (e.g., 'Try search_capabilities() first'). Violates recovery-guide pattern.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) present. run_workflow and generate_report are WRITE operations but lack destructiveHint. Agents cannot distinguish safe from risky calls.