AINumbers Fintech Intelligence Suite

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/8498d0819c941fdb731f9e10f5d93ee929026919cb111a42149821b48b5ac180.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Output schema: call describe_tool("validate_openids_homeowners_record").

Input Schema

TableJSON Schema

Name	Required	Description
`compute`	No	Compute 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_hashes`	No	execution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
`parent_tool_ids`	No	tool_id values matching parent_hashes, in the same order.
`policy_parameters`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous 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"
-}New value: +null

Changed1 schema field changedSep 3, 2026

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"
+}

AddedJul 5, 2026

TDQS

B3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial non-obvious behavior: transient processing with no storage/logging/retention, deterministic execution, compute-mode routing with browser delegation URLs, and AP2 artifact export with execution_hash. This is genuine value beyond the structured fields.

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?

Sentences are individually tight, but the description is dominated by infrastructure and provenance jargon before it conveys anything about the validation itself, and the FV-status hash/URL line is low-value for an agent choosing a tool. Front-loading of core purpose is weak.

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 nested objects, no output schema, and no annotations on the domain logic, the description covers compute routing and provenance adequately but omits what the validator returns or what a passing/failing result means. It defers detail to describe_tool, which is a reasonable stopgap but leaves the core semantics thin.

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 largely restates the compute-mode enum and adds no field-name or format guidance for policy_parameters beyond pointing at the manifest. Baseline 3 when the schema does the heavy lifting.

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

Purpose3/5

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

The description names a specific verb and resource ('validate' + 'openIDS Homeowners Record') and labels the node a compliance_mandate compute node. However, it never states what the validation actually checks or what a homeowner record contains, and with dozens of validate_* siblings it does nothing to differentiate itself. The purpose is identifiable but shallow.

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 when-to-use guidance relative to alternatives, no prerequisites, and no condition under which validation is warranted. The only usage instruction is 'Use synthetic or anonymised inputs only,' which is an input-safety note, not selection guidance.

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 tools Inspect

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.

openIDS Homeowners Record Validator

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources