Skip to main content
Glama

AINumbers Fintech Intelligence Suite

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/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.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").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "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.5/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/destructive annotations, the description discloses that the node is deterministic, that inputs are processed transiently and not stored or logged, that server-side kernels run on Cloudflare Workers, and that the export carries an execution_hash for chain provenance. That is substantive behavioral context an annotation cannot express. It stops short of describing the returned artifact's shape, deferring that to describe_tool.

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

Conciseness3/5

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

The structure is partially front-loaded but wastes the opening on a tautology and a repeated 'deterministic compute node' sentence, burying the actual purpose in the closing Summary. The docs URL and a 64-character FV-status hash with the 'snapshot, not a subscription' disclaimer consume space with no evident value for tool selection or invocation. The compute-mode paragraph duplicates the input schema verbatim in substance.

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?

For a 4-parameter tool with a nested object and no output schema, the description covers safety, determinism, retention, provenance chaining, and gives an output field name (chain_config). However it explicitly punts return-value detail to describe_tool and never clarifies the nested 'mandate' payload or what a gated-chain config contains. Adequate but leaves an agent to make a follow-up call to understand results.

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 the schema already documents compute, parent_hashes, parent_tool_ids, and policy_parameters. The description's compute-mode paragraph largely restates the schema's own compute description, and it adds nothing about how parent_hashes/parent_tool_ids pair up or what shape 'mandate' takes. Baseline 3 is appropriate when structured fields carry the semantics.

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 'Summary' clause gives a specific verb and resource: it compiles a §22 Work Mandate document into a deterministic §21.4 gated-chain config and outputs chain_config. That is meaningfully distinct from generic builders like build_chaingraph, though the description never names or contrasts with the nearest siblings (ap2_aml_mandate_builder, build_google_ap2_mandate, draft_ap2_mandate_credential). The opening line is tautological ('Work Mandate Compiler: OpenChainGraph compute node') and the §-section references are opaque without external context.

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?

There is real guidance on compute mode selection (auto/server/browser, gpu:true always delegates), plus a hard constraint to use synthetic or anonymised inputs only. What is missing is routing guidance versus alternative tools that also produce AP2 mandates, so an agent cannot tell from this text alone when to pick this compiler over a sibling builder.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.