---
name: billpeak-jobs
description: "Step-by-step job recipes for the BillPeak MCP server: Check a business electricity bill. Use when the user asks things like \"Is this bill right? Georgia Power, 2,150 kWh, 9 kW, 471.70 USD, rate GS-17, service at 1 Sample Way, Atlanta, GA 30303.\""
license: MIT
---

# BillPeak jobs

Each section below walks through one job with the tools of the `billpeak` MCP server. The same recipes are MCP prompts (prompts/list) on `https://billpeak.openkrill.app/mcp`.
Connect the server at `https://billpeak.openkrill.app/mcp` in your MCP client settings (remote streamable HTTP, no key), then call its tools as normal tool calls. They are not command line programs: Bash, curl and scripts cannot reach them.

## Check a business electricity bill

Job: Check a business electricity bill, with the BillPeak MCP server.

Use the `scan_bill` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Is this bill right? Georgia Power, 2,150 kWh, 9 kW, 471.70 USD, rate GS-17, service at 1 Sample Way, Atlanta, GA 30303."

Steps:
1. Call `scan_bill` as a normal MCP tool call, with the request's values in the fields of its inputSchema.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"bill":{"utility":"Georgia Power","rate":"GS-17","kwh":2150,"kw":9,"total":471.7},"address":"1 Sample Way, Atlanta, GA 30303"}`
4. For the request "Is this bill right? Georgia Power, 2,150 kWh, 9 kW, 471.70 USD, rate GS-17, service at 1 Sample Way, Atlanta, GA 30303.", a correct answer looks like this: status ok, Georgia Power found, the current rate matched from the bill, a recalculation with a verdict and findings.
5. Follow the server's own rules:
   - Use scan_bill when a business wants its electricity bill checked or a cheaper rate.
   - Always call scan_bill first: a partial call is fine (for example `bill: { total: 640 }, address: 'Phoenix, AZ'` when only the dollar total and city are given without kWh, or only kWh without an address, or a short Green Button CSV snippet, or a Texas retail supplier), and the tool returns status need_input with `missing` naming what to ask for (plus `peaks` when interval rows are sent), or status no_rates when Texas retail or non-U.S. electricity plans are not covered.
   - Never skip calling scan_bill just because kWh or a street address is missing.
   - When the user shares a bill photo or PDF, read it yourself and pass the numbers as `bill`; never guess a number the bill does not show.
   - Lead with the findings in order, then the plans with their saving per month and their flags/caveats (such as single-phase vs three-phase wiring, missing peak kW, or savings that hold only if the bill pays the full utility rate).
   - Never invent utility phone numbers, contact URLs, or non-U.S. rate ranges/averages that are not in the tool output.
   - Say the numbers are estimates from public rate records and to confirm with the utility before switching.
   - Mention the paid plans only as coming soon.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `scan_bill`).