Skip to main content
Glama

AINumbers Fintech Intelligence Suite

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

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": "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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, and the description adds genuinely non-obvious behavior beyond them: deterministic computation, transient input processing with no storage or logging, a 'synthetic or anonymised inputs only' caveat, no clock reads (now_unix must be caller-supplied), and an AP2 artifact export with execution_hash. The remaining text (GPU/kernel routing, FV-status receipt, artifact URL) is largely infrastructure boilerplate rather than decision-relevant behavior.

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 core purpose, inputs, and outputs are compressed into the last two sentences, while the front of the description is dominated by compute-kernel routing, a release URL, and a long hash-verification receipt that an invoking agent does not need to act. Front-loading is poor — the most important information arrives last — though the individual sentences are not redundant.

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?

There is no output schema, and the description compensates by listing the returned fields and describing the compute-mode behavior, data-retention stance, and provenance chaining. What is missing is any statement of prerequisite inputs (where the mandate object comes from, what constitutes a valid scope) and any failure/verdict semantics, which for a compliance validator leaves a meaningful gap.

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 description coverage is 100%, which sets a baseline of 3, but the nested policy_parameters object is opaque in the schema (mandate and now_unix are declared only as empty objects), and the description fills that gap by enumerating the mandate's components and stating that now_unix is caller-supplied with no clock reads. The brief explanation of the outputs (gaps, has_intent, has_scope, not_expired, verdict) further clarifies what the parameters feed, putting this slightly above baseline.

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 sentence gives a specific verb and resource: 'Validate an agent on-behalf-of (OBO) mandate' with the fields it checks (subject, bounded scope array, intent, non-expired validity window). It is clear on its own, but it never names or distinguishes itself from near-neighbours such as validate_a2a_x402_mandate, validate_ap2_mandate_credential, or check_agent_token_scope, so an agent still has to infer the boundary.

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?

Usage context is implied through pipeline positioning ('Consumes upstream artifacts from: art-150...' and 'Output feeds: art-152...'), which hints at where in a chain it belongs, and the compute-mode paragraph tells you how execution is routed. However, there is no explicit 'use this when X, prefer sibling Y when Z' guidance, which matters given the large number of mandate-validation siblings.

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.