compare_semantic_equivalence
Compare two payloads under the dual-hash design: content_hash is content_hash normalizes field order and numeric formatting. Semantic comparison preserves field roles; renaming requires an explicit bijection. With supplied rules, scalar types and whitespace remain significant. Structural similarity alone does not establish decision equivalence.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"api_key": "<api_key>",
"payload_a": "<payload_a>",
"payload_b": "<payload_b>"
},
"name": "compare_semantic_equivalence"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | GeodesicAI API key (gai_...) | |
| rules_a | No | Derivation rules for A | |
| rules_b | No | Derivation rules for B | |
| payload_a | Yes | First structured payload (arbitrary JSON object) | |
| payload_b | Yes | Second structured payload to compare against payload_a | |
| constraints_a | No | Formal constraints for A | |
| constraints_b | No | Formal constraints for B | |
| field_mapping | No | Explicit one-to-one field renaming from A to B |