Skip to main content
Glama

AINumbers Fintech Intelligence Suite

by co.ainumbers

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/e5ebd9cab6d424d5a202b2144bf9dacc14abf4ed24f3f0ac3adbecdd87c14872.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched.

Input Schema

TableJSON 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". See the tool's manifest for field names.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
chain_configNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+}
  2. Added

TDQS

A3.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint and idempotentHint annotations: discloses that inputs are processed transiently, not stored/logged/retained, that compute can delegate to browser for gpu:true nodes, and that output includes execution_hash for provenance. This materially informs how an agent should treat inputs.

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 first two sentences redundantly repeat 'OpenChainGraph compute node' verbatim. The description includes tangential FV-status and URL content that is not needed for tool invocation, and the useful behavioral information is buried under repetition and extra links.

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?

The description covers compute modes, data handling, and output artifact characteristics, and is backed by a complete schema and output schema. It lacks explicit alternative routing but is otherwise sufficiently complete for correct invocation.

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?

Input schema coverage is 100%, so parameters are already documented. The description reinforces the compute parameter's modes and policy_parameters behavior, but adds no new meaning beyond what the schema provides. Baseline 3 is appropriate.

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 the tool is an OpenChainGraph compute node for governance_mandate that exports an AP2 artifact with execution_hash, giving a specific verb and resource. It distinguishes itself by the governance_mandate scope, but does not explicitly differentiate from sibling compile/build tools like build_ap2_cartmandate_hashchain.

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?

The description explains when server-side vs browser compute is used and instructs to use synthetic or anonymised inputs, providing some usage context. However, it never explicitly states when to choose this tool over alternatives, so guidance is implied rather than explicit.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.9/5.0
Disambiguation1/5

With 698 tools covering overlapping regulatory and compliance domains, many tools have near-identical names and purposes (e.g., check_genius_reserve_disclosure vs check_genius_reserve_disclosure_conformance, multiple DORA incident classifiers, several AP2 mandate validators). The highly templated descriptions further reduce distinctiveness, making reliable tool selection by an agent effectively impossible.

Naming Consistency4/5

The overwhelming majority of tools follow a consistent snake_case verb_noun pattern (assess_*, build_*, compute_*, validate_*, verify_*). Minor deviations exist (camt053_parse, workbook_evaluate, ha_gate_status, sdjwt_issue, etc.), but they are a small fraction of the total and follow recognizable domain-prefix conventions.

Tool Count1/5

698 tools is an extreme oversizing for any server, far beyond the 50+ threshold for a low score. Even with dedicated search/discovery tools, this unwieldy surface guarantees cognitive overload, high misselection risk, and severe practical usability problems.

Completeness4/5

The suite covers an extraordinarily broad range of fintech/regulatory domains — capital adequacy, AML, payments, crypto, AI governance, trade finance, and many verification/recompute lifecycles. Obvious gaps are difficult to identify, though the set is not a coherent single lifecycle and some niche areas are inevitably absent.

Resources