Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Privi Car: cheapest EV charging plan

car_charge_plan

Pick which time slots to charge in so the car has the energy it needs at the lowest cost. Runs on the CVaR-QAOA quantum simulator and against exact search; the signed receipt shows both and the plan is the proven best. Returns the slots, cost, and savings over charging right away. A plan only: nothing is sent to a charger.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "price_per_kwh": "<price_per_kwh>",
      "charger_kw": "<charger_kw>",
      "energy_needed_kwh": "<energy_needed_kwh>"
    },
    "name": "car_charge_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
charger_kwYesCharger power in kW
slot_hoursNoLength of one slot in hours (default 1)
price_per_kwhYesElectricity price for each time slot before departure (2-16 slots)
energy_needed_kwhYesEnergy to add before departure, in kWh
switch_penalty_usdNoCost charged for each start/stop, to favor one continuous session (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, it discloses the solving method (CVaR-QAOA simulator plus exact search), that a signed receipt proves optimality, and that the result is a plan with no actuation - useful context given readOnlyHint=false, which alone would leave an agent unsure whether calling this mutates state. It does not say what artifact the non-read-only behavior produces or where the receipt lives, which keeps it off a 5.

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?

Front-loaded with what the tool does and what it returns, with zero filler sentences. The middle sentence about CVaR-QAOA and the signed receipt is dense and slightly jargon-heavy, but it does earn its place by justifying trust in the output.

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

Completeness4/5

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

With no output schema, the description usefully states the return shape (slots, cost, savings) and clarifies the no-actuation boundary for a five-parameter tool. What remains thin - parameter interactions like the switch penalty and the slot-count range - is covered by the schema's own descriptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all five parameters are already documented in the schema; the description adds no parameter-level detail and does not explain slot_hours or switch_penalty_usd trade-offs. Baseline 3 applies since the schema carries the semantic load.

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 states a concrete verb and resource ('pick which time slots to charge in') plus the objective ('lowest cost') and what is returned ('the slots, cost, and savings'). It is clearly an optimization/planning tool, distinct in kind from the car_* lookup and key-management 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 implied by the framing 'so the car has the energy it needs at the lowest cost', and the closing line 'A plan only: nothing is sent to a charger' hints at a boundary, but no when-to-use condition, prerequisite, or named alternative is given. An agent must infer the trigger conditions on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Privi Quantum toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources