Demand-response aggregator for agent fleets

Most tools have distinct roles across the curtailment lifecycle: manifest registration, event opening, actuals/history reporting, probing, attestation, and settlement. The probe-related tools (run_probe, issue_probe_challenge, capsule_resume, attestation) have some conceptual overlap, but their descriptions differentiate them enough for an agent to choose correctly.

Names use snake_case throughout, but conventions are mixed: most are verb_noun (add_actuals, open_event, register_manifest), while others are noun-based (attestation, capsule_resume) or a bare verb (settle). The set remains readable, but the pattern is not fully predictable.

Nine tools is well-scoped for a demand-response lifecycle covering registration, event execution, measurement, verification, and settlement. Each tool appears to earn its place without obvious redundancy.

The surface covers opening events, reporting data, probing, attestation, and settlement, but lacks obvious read/inspection or lifecycle-management operations such as listing events, checking event status, aborting/cancelling an event, or deregistering a manifest. Agents may hit dead ends when they need to inspect state rather than act.