Skip to main content
Glama

AINumbers Fintech Intelligence Suite

by co.ainumbers
OverviewDiscussionsAdmin

Work Mandate Compiler

compile_work_mandate
Read-onlyIdempotent

Work Mandate Compiler: OpenChainGraph compute node (governance_mandate). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic or anonymised inputs only. Exports an AP2 artifact with execution_hash for chain provenance. Open at: https://ainumbers.co/chaingraph/art-274-compile-work-mandate.html FV-status (published/proven/still-trusted for this spec): /fv-status/ca4e1dca8343f788a296161f0e19712f7afb7e5eaec0431081e715a4cc34b784.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Compiles a §22 Work Mandate document into a deterministic §21.4 gated-chain config. Outputs: chain_config. Output schema: call describe_tool("compile_work_mandate").

Input Schema

NameRequiredDescriptionDefault
computeNoCompute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always return browser delegation URL. gpu:true nodes always delegate.
parent_hashesNoexecution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
parent_tool_idsNotool_id values matching parent_hashes, in the same order.
policy_parametersNoInput parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "server". Required: mandate. Unknown keys are refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changed
    • changedInput schema / properties / policy_parameters / description
      Previous value: -"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". See the tool's manifest for field names."New value: +"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". Required: mandate. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
+  "mandate": {}
+}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
-  "type": "string"
-}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "chain_config": {
-      "properties": {
-        "steps": {
-          "items": {
-            "properties": {
-              "gate": {
-                "properties": {
-                  "default": {
-                    "type": "string"
-                  },
-                  "input": {
-                    "type": "string"
-                  },
-                  "rules": {
-                    "items": {
-                      "properties": {
-                        "next": {
-                          "type": "string"
-                        },
-                        "op": {
-                          "type": "string"
-                        },
-                        "value": {
-                          "type": "boolean"
-                        }
-                      },
-                      "type": "object"
-                    },
-                    "type": "array"
-                  }
-                },
-                "type": "object"
-              },
-              "id": {
-                "type": "string"
-              },
-              "tool_id": {
-                "type": "string"
-              }
-            },
-            "type": "object"
-          },
-          "type": "array"
-        }
-      },
-      "type": "object"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "chain_config": {
+      "properties": {
+        "steps": {
+          "items": {
+            "properties": {
+              "gate": {
+                "properties": {
+                  "default": {
+                    "type": "string"
+                  },
+                  "input": {
+                    "type": "string"
+                  },
+                  "rules": {
+                    "items": {
+                      "properties": {
+                        "next": {
+                          "type": "string"
+                        },
+                        "op": {
+                          "type": "string"
+                        },
+                        "value": {
+                          "type": "boolean"
+                        }
+                      },
+                      "type": "object"
+                    },
+                    "type": "array"
+                  }
+                },
+                "type": "object"
+              },
+              "id": {
+                "type": "string"
+              },
+              "tool_id": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  5. Added

TDQS

A3.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive, consistent with the described behavior), the description discloses execution semantics: deterministic server-side computation on Cloudflare Workers for gpu:false nodes with registered kernels, browser delegation for gpu:true, transient no-store/no-log processing, and an AP2 artifact with execution_hash for chain provenance. That is exactly the behavioral context structured fields cannot carry.

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

Conciseness2/5

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

The payload is buried at the end while the opening twice repeats 'OpenChainGraph compute node,' and a 64-character FV-status file hash plus a raw URL consume substantial space for little selection value. The one sentence an agent actually needs (the compile summary) is last rather than front-loaded.

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

Completeness3/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 does cover the return shape briefly ('Outputs: chain_config') and points to describe_tool for the schema. However, for a compute tool with a nested `policy_parameters.mandate` payload it never indicates what a §22 Work Mandate document should contain, leaving the most likely source of miscalls unexplained.

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 description coverage is 100%, so compute modes, parent_hashes/parent_tool_ids chaining, and the required `mandate` key are already documented. The description restates the compute:'auto'/browser behavior without adding syntax or shape detail for the nested `mandate` object, so it does not exceed the schema.

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 final summary sentence is precise: 'Compiles a §22 Work Mandate document into a deterministic §21.4 gated-chain config,' naming a specific verb, input artifact, and output artifact. The opening repeats the tautological 'Work Mandate Compiler: OpenChainGraph compute node' framing, and no sibling (e.g. build_chaingraph, agentic_mandate_sandbox, build_ap2_cartmandate_hashchain) is named to differentiate.

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?

It gives a real constraint — 'Use synthetic or anonymised inputs only' — and explains the compute-mode choice, but offers no guidance on when to pick this tool over the many other mandate/chaingraph builders in the sibling list, and no exclusions or prerequisites for the input document.

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

All AINumbers Fintech Intelligence Suite 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