Skip to main content
Glama

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/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Validates homeowners insurance data records against the openIDS Homeowners Data Standard v1.0 (AAIS / Linux Foundation, November 2025) -- the first free open (Apache-2.0) insurance data standard. Outputs: error_count, errors, not_legal_advice, pii_fields_found, pii_note, record_valid, regulatory_basis, section_results, sections_present, sections_required, standard_version, table_source, warning_count, warnings. Output schema: call describe_tool("validate_openids_homeowners_record").

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

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: record. 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: record. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "record": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • 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
  4. 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"
      +}
  5. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is pre-cleared; the description still adds substantive behavior: inputs are processed transiently and not stored or logged, gpu:true nodes always delegate to the browser, and the call exports an AP2 artifact carrying an execution_hash for chain provenance. That last point is real behavioral information an agent cannot get from the annotations. It does not say what happens on validation failure versus malformed input, which keeps it below 5.

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 opening is repetitive — 'OpenChainGraph compute node (compliance_mandate). Deterministic OpenChainGraph compute node.' says the same thing twice. A documentation URL and a long FV-status hash are not decision-relevant for tool selection and push the actual purpose to the end. The 14 output field names are a useful list, but the whole is not front-loaded.

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?

There is no output schema, but the description compensates by enumerating the returned fields (record_valid, error_count, errors, section_results, pii_fields_found, regulatory_basis, etc.), which is enough for an agent to know what it will receive. Privacy handling, compute delegation and provenance export are all covered. The remaining gap is guidance on interpreting failures and no pointer to how the record should be structured.

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, including the compute enum semantics and the record requirement. The description largely restates the compute behavior and adds no new meaning about parent_hashes ordering or what shape the record object must take. Baseline 3 applies when the schema carries the parameter load.

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' sentence gives a specific verb and resource: validates homeowners insurance data records against the openIDS Homeowners Data Standard v1.0, with a named version and publisher. The problem is placement — the actual purpose appears only after several sentences of OpenChainGraph compute-node boilerplate, so an agent skimming the front of the description sees infrastructure jargon before it learns what is validated. It is distinguishable from the validate_* siblings by domain, but no sibling is named.

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 one genuine usage constraint: 'Use synthetic or anonymised inputs only.' Beyond that, the compute-mode guidance explains parameter behavior rather than when to choose this tool over an alternative. No when-not-to-use conditions and no reference to related insurance validators (e.g. lint_insurance_evidence_freshness) that an agent might confuse it with.

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.