Skip to main content
Glama

AINumbers Fintech Intelligence Suite

by co.ainumbers
OverviewDiscussionsAdmin

Agent On-Behalf-Of (OBO) Mandate Validator

validate_agent_obo_mandate
Read-onlyIdempotent

Agent On-Behalf-Of (OBO) Mandate Validator: OpenChainGraph compute node (compliance_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. Consumes upstream artifacts from: art-150-mcp-tool-scope-revocation-auditor. Output feeds: art-152-mcp-task-lifecycle-validator. Open at: https://ainumbers.co/chaingraph/art-151-agent-obo-mandate-validator.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: Validate an agent on-behalf-of (OBO) mandate: subject (the user being represented), bounded scope array, intent string, and a non-expired validity window (caller-supplied now_unix, no clock reads). Outputs: gaps, has_intent, has_scope, has_subject, not_expired, verdict. Output schema: call describe_tool("validate_agent_obo_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". 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\". Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
+  "mandate": {},
+  "now_unix": {}
+}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
-  "type": "string"
-}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "gaps": {
-      "type": "array"
-    },
-    "has_intent": {
-      "type": "boolean"
-    },
-    "has_scope": {
-      "type": "boolean"
-    },
-    "has_subject": {
-      "type": "boolean"
-    },
-    "not_expired": {
-      "type": "boolean"
-    },
-    "verdict": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "gaps": {
+      "type": "array"
+    },
+    "has_intent": {
+      "type": "boolean"
+    },
+    "has_scope": {
+      "type": "boolean"
+    },
+    "has_subject": {
+      "type": "boolean"
+    },
+    "not_expired": {
+      "type": "boolean"
+    },
+    "verdict": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  5. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: server-side versus browser execution, gpu:true delegation, transient non-stored inputs, AP2 artifact export with execution_hash, upstream artifact consumption, and caller-supplied now_unix with no clock reads. It does not contradict the read-only, idempotent, non-destructive annotations.

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 description is bloated with OpenChainGraph boilerplate, URLs, a long FV-status hash, and provenance details before the core summary appears. The key validation purpose is buried, so the text is not front-loaded and much of it does not help an agent quickly select or invoke the tool.

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?

For a tool with no output schema and a nested policy object, the description is fairly complete: it lists output fields, explains compute modes, and summarizes mandate inputs. It could go further on verdict values and gap semantics, but it provides enough context to call the tool correctly.

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?

Schema coverage is 100%, so the structured schema already documents the top-level parameters. The description adds meaningful semantics for the nested policy mandate by naming subject, bounded scope array, intent string, and now_unix, though it does not elaborate on parent_hashes or parent_tool_ids beyond the schema.

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 specific operation: validating an agent on-behalf-of (OBO) mandate, including the subject, bounded scope array, intent, and non-expired validity window. This is a specific verb+resource and is distinguishable from generic mandate or AP2 validation siblings.

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 gives execution-mode guidance for compute auto/server/browser and says to use synthetic or anonymised inputs, which is useful. However, it does not state when to use this tool versus alternatives such as validate_ap2_mandate_credential, validate_ap2_mandate_chain, or authorize_payment_against_mandate, so routing guidance is only implied.

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