Skip to main content
Glama

AINumbers Fintech Intelligence Suite

by co.ainumbers
OverviewDiscussionsAdmin

openIDS Homeowners Record Validator

validate_openids_homeowners_record
Read-onlyIdempotent

openIDS Homeowners Record 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. Open at: https://ainumbers.co/chaingraph/art-256-validate-openids-homeowners-record.html FV-status (published/proven/still-trusted for this spec): /fv-status/dfdd7083d50dfec46270d5ca2c4a06852efd98bdc1ae8d20e3d3b191e9b14ac7.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
errorsNo
pii_noteNo
warningsNo
error_countNo
record_validNo
table_sourceNo
warning_countNo
section_resultsNo
not_legal_adviceNo
pii_fields_foundNo
regulatory_basisNo
sections_presentNo
standard_versionNo
sections_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "error_count": {
+      "type": "integer"
+    },
+    "errors": {
+      "type": "array"
+    },
+    "not_legal_advice": {
+      "type": "string"
+    },
+    "pii_fields_found": {
+      "type": "array"
+    },
+    "pii_note": {
+      "type": "string"
+    },
+    "record_valid": {
+      "type": "boolean"
+    },
+    "regulatory_basis": {
+      "type": "string"
+    },
+    "section_results": {
+      "properties": {
+        "coverage": {
+          "properties": {
+            "field_errors": {
+              "type": "array"
+            },
+            "present": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        "insured_location": {
+          "properties": {
+            "field_errors": {
+              "type": "array"
+            },
+            "present": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        "policy": {
+          "properties": {
+            "field_errors": {
+              "type": "array"
+            },
+            "present": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        "premium": {
+          "properties": {
+            "field_errors": {
+              "type": "array"
+            },
+            "present": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "sections_present": {
+      "type": "integer"
+    },
+    "sections_required": {
+      "type": "integer"
+    },
+    "standard_version": {
+      "type": "string"
+    },
+    "table_source": {
+      "type": "string"
+    },
+    "warning_count": {
+      "type": "integer"
+    },
+    "warnings": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

C2.7/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description usefully adds that inputs are processed transiently with no storage or logging, that an AP2 artifact with execution_hash is exported, and that gpu:true nodes always delegate to the browser. It does not contradict the readOnly annotation, and this is meaningful context beyond the structured hints.

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 title is redundantly repeated as the first clause and again paraphrased as 'Deterministic OpenChainGraph compute node'. The trailing FV-status sentence with a long URL and 64-char hash is information-dense but poorly integrated, making the whole entry feel padded around a missing core.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema and annotations exist, so return format and safety are covered, but the description omits the one thing that matters most: what records are validated and against which rule set. For a compliance_mandate compute node with 4 params, this leaves the agent unable to judge applicability.

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 all four parameters are already documented by the schema, including the compute enum and the parent_hashes/parent_tool_ids ordering rule. The description repeats the compute semantics and defers policy_parameters to 'the tool's manifest', adding little beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what a homeowners record validation actually checks, what a valid vs invalid record looks like, or what 'openIDS' resolves to. It restates the title and then pivots entirely to compute-node infrastructure (compute modes, artifact export, provenance), so an agent cannot distinguish the substantive purpose from dozens of sibling validate_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this validator versus alternatives such as validate_openvex_statement, validate_mletr_record, or the other record validators. The compute-mode explanation ('auto' vs 'browser') describes how execution happens, not when this tool is the right choice.

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