viridis-agent-fleet

Overview Schema Source Related Servers Discussions Admin

compute-ledger__record_work

Record agent compute work to an energy/carbon ledger. Calculate energy from power and duration, determine carbon emissions from grid intensity, and optionally validate against the Landauer limit to reject physically impossible claims.

Instructions

[compute-ledger — compute-is-carbon energy/carbon ledger] Record a unit of agent compute work. energy_j = power_w * duration_s; carbon_g follows from grid intensity. If bit_ops is declared, the entry is validated against the Landauer floor (bit_ops * kB * T * ln2) — physically impossible claims are rejected. Idempotent on entry_id.

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": {
      "agent_id": "<agent_id>",
      "entry_id": "<entry_id>",
      "power_w": "<power_w>",
      "duration_s": "<duration_s>"
    },
    "name": "compute-ledger__record_work"
  }
}

Input Schema

Name	Required	Description	Default
`task`	No
`bit_ops`	No
`power_w`	Yes
`agent_id`	Yes
`entry_id`	Yes
`duration_s`	Yes
`temperature_k`	No
`price_minor_per_kwh`	No
`grid_intensity_g_per_kwh`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.12Jul 28, 2026
Removedv0.1.11Jul 18, 2026
Changed16 schema fields changedv0.1.9Jul 16, 2026
- removedInput schema / properties / agent_id / title
```
Removed value: -"Agent Id"
```
- removedInput schema / properties / bit_ops / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / bit_ops / default
```
Removed value: -null
```
- removedInput schema / properties / bit_ops / title
```
Removed value: -"Bit Ops"
```
- addedInput schema / properties / bit_ops / type
```
Added value: +"number"
```
- removedInput schema / properties / duration_s / title
```
Removed value: -"Duration S"
```
- removedInput schema / properties / entry_id / title
```
Removed value: -"Entry Id"
```
- removedInput schema / properties / grid_intensity_g_per_kwh / title
```
Removed value: -"Grid Intensity G Per Kwh"
```
- removedInput schema / properties / power_w / title
```
Removed value: -"Power W"
```
- removedInput schema / properties / price_minor_per_kwh / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / price_minor_per_kwh / default
```
Removed value: -null
```
- removedInput schema / properties / price_minor_per_kwh / title
```
Removed value: -"Price Minor Per Kwh"
```
- addedInput schema / properties / price_minor_per_kwh / type
```
Added value: +"number"
```
- removedInput schema / properties / task / title
```
Removed value: -"Task"
```
- removedInput schema / properties / temperature_k / title
```
Removed value: -"Temperature K"
```
- removedInput schema / title
```
Removed value: -"record_workArguments"
```
Changed16 schema fields changedJul 13, 2026
- addedInput schema / properties / agent_id / title
```
Added value: +"Agent Id"
```
- addedInput schema / properties / bit_ops / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / bit_ops / default
```
Added value: +null
```
- addedInput schema / properties / bit_ops / title
```
Added value: +"Bit Ops"
```
- removedInput schema / properties / bit_ops / type
```
Removed value: -"number"
```
- addedInput schema / properties / duration_s / title
```
Added value: +"Duration S"
```
- addedInput schema / properties / entry_id / title
```
Added value: +"Entry Id"
```
- addedInput schema / properties / grid_intensity_g_per_kwh / title
```
Added value: +"Grid Intensity G Per Kwh"
```
- addedInput schema / properties / power_w / title
```
Added value: +"Power W"
```
- addedInput schema / properties / price_minor_per_kwh / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / price_minor_per_kwh / default
```
Added value: +null
```
- addedInput schema / properties / price_minor_per_kwh / title
```
Added value: +"Price Minor Per Kwh"
```
- removedInput schema / properties / price_minor_per_kwh / type
```
Removed value: -"number"
```
- addedInput schema / properties / task / title
```
Added value: +"Task"
```
- addedInput schema / properties / temperature_k / title
```
Added value: +"Temperature K"
```
- addedInput schema / title
```
Added value: +"record_workArguments"
```
Changed16 schema fields changedJul 13, 2026
- removedInput schema / properties / agent_id / title
```
Removed value: -"Agent Id"
```
- removedInput schema / properties / bit_ops / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / bit_ops / default
```
Removed value: -null
```
- removedInput schema / properties / bit_ops / title
```
Removed value: -"Bit Ops"
```
- addedInput schema / properties / bit_ops / type
```
Added value: +"number"
```
- removedInput schema / properties / duration_s / title
```
Removed value: -"Duration S"
```
- removedInput schema / properties / entry_id / title
```
Removed value: -"Entry Id"
```
- removedInput schema / properties / grid_intensity_g_per_kwh / title
```
Removed value: -"Grid Intensity G Per Kwh"
```
- removedInput schema / properties / power_w / title
```
Removed value: -"Power W"
```
- removedInput schema / properties / price_minor_per_kwh / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / price_minor_per_kwh / default
```
Removed value: -null
```
- removedInput schema / properties / price_minor_per_kwh / title
```
Removed value: -"Price Minor Per Kwh"
```
- addedInput schema / properties / price_minor_per_kwh / type
```
Added value: +"number"
```
- removedInput schema / properties / task / title
```
Removed value: -"Task"
```
- removedInput schema / properties / temperature_k / title
```
Removed value: -"Temperature K"
```
- removedInput schema / title
```
Removed value: -"record_workArguments"
```
First observedJul 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses energy/carbon calculation, Landauer floor validation, rejection of physically impossible claims, and idempotency. This is transparent, though it could mention error handling or side effects more explicitly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, dense paragraph of four sentences with no unnecessary words. It conveys essential information efficiently.

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?

Given the tool's complexity (9 parameters, physics validation, no output schema), the description covers the main behavioral aspects and parameter relationships. However, it could include more detail on return value or error scenarios.

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

Parameters4/5

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

The description explains key parameters (power_w, duration_s, bit_ops, grid_intensity_g_per_kwh) with formulas and validation logic, compensating for the 0% schema description coverage. However, it does not cover all 9 parameters (e.g., task, temperature_k, price_minor_per_kwh), leaving some ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool records a unit of agent compute work, provides the calculation formula, and mentions validation against Landauer floor. It distinguishes from sibling tools by specifying the context (compute-is-carbon ledger) and the specific action (recording work).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool (to record agent compute work) and includes details like idempotency on entry_id and validation of physical bounds. However, it does not explicitly contrast with alternative tools like compute-ledger__footprint or attest, but the unique purpose is clear.

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

Deploy Server