Skip to main content
Glama

AINumbers Fintech Intelligence Suite

Sanctions Screening-Program Quality Scorer

score_sanctions_screening_quality
Read-onlyIdempotent

Sanctions Screening-Program Quality Scorer: OpenChainGraph compute node (model_governance). 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-92-screening-list-coverage-checker, art-93-fuzzy-match-calibration-scorer. Output feeds: cry-05-agent-action-audit-trail-aggregator. Open at: https://ainumbers.co/chaingraph/art-97-sanctions-screening-quality-scorer.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: Wolfsberg-aligned screening-program quality scorecard: list coverage + match calibration + alert tuning + escalation workflow + model validation -> composite program-conformance grade and improvement priorities. Outputs: component_scores, component_weights, composite_pct, improvement_priorities, note, program_grade, reference_version, wolfsberg_note. Output schema: call describe_tool("score_sanctions_screening_quality").

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

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: +{
      +  "inputs": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "component_scores": {
      -      "properties": {
      -        "alert_tuning": {
      -          "type": "integer"
      -        },
      -        "escalation_workflow": {
      -          "type": "integer"
      -        },
      -        "list_coverage": {
      -          "type": "integer"
      -        },
      -        "match_calibration": {
      -          "type": "integer"
      -        },
      -        "model_validation": {
      -          "type": "integer"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "component_weights": {
      -      "properties": {
      -        "alert_tuning": {
      -          "type": "integer"
      -        },
      -        "escalation_workflow": {
      -          "type": "integer"
      -        },
      -        "list_coverage": {
      -          "type": "integer"
      -        },
      -        "match_calibration": {
      -          "type": "integer"
      -        },
      -        "model_validation": {
      -          "type": "integer"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "composite_pct": {
      -      "type": "integer"
      -    },
      -    "improvement_priorities": {
      -      "items": {
      -        "properties": {
      -          "action": {
      -            "type": "string"
      -          },
      -          "current_score": {
      -            "type": "integer"
      -          },
      -          "dimension": {
      -            "type": "string"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "note": {
      -      "type": "string"
      -    },
      -    "program_grade": {
      -      "type": "string"
      -    },
      -    "reference_version": {
      -      "type": "string"
      -    },
      -    "wolfsberg_note": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "component_scores": {
      +      "properties": {
      +        "alert_tuning": {
      +          "type": "integer"
      +        },
      +        "escalation_workflow": {
      +          "type": "integer"
      +        },
      +        "list_coverage": {
      +          "type": "integer"
      +        },
      +        "match_calibration": {
      +          "type": "integer"
      +        },
      +        "model_validation": {
      +          "type": "integer"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "component_weights": {
      +      "properties": {
      +        "alert_tuning": {
      +          "type": "integer"
      +        },
      +        "escalation_workflow": {
      +          "type": "integer"
      +        },
      +        "list_coverage": {
      +          "type": "integer"
      +        },
      +        "match_calibration": {
      +          "type": "integer"
      +        },
      +        "model_validation": {
      +          "type": "integer"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "composite_pct": {
      +      "type": "integer"
      +    },
      +    "improvement_priorities": {
      +      "items": {
      +        "properties": {
      +          "action": {
      +            "type": "string"
      +          },
      +          "current_score": {
      +            "type": "integer"
      +          },
      +          "dimension": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "program_grade": {
      +      "type": "string"
      +    },
      +    "reference_version": {
      +      "type": "string"
      +    },
      +    "wolfsberg_note": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Added

TDQS

B3.4/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, closed-world), and the description adds genuinely non-structured behavior: determinism, transient processing with no storage or logging, an AP2 artifact carrying execution_hash for chain provenance, and a verifiable offline FV-status receipt. The compute-mode paragraph (server vs browser delegation, gpu:true always delegating) is behaviorally relevant but largely duplicates the `compute` parameter description in the schema. No contradiction with the read-only annotations.

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 description is badly front-loaded: it opens with framework metadata and a full restatement of the compute-mode mechanics, then buries the actual purpose under a 'Summary:' label well past the halfway point. Substantial text is spent on a raw FV-status hash URL and a landing-page link that add little for an agent deciding whether to call. The output field list is the most useful part and should be far earlier.

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, but the description compensates by enumerating the return fields (component_scores, component_weights, composite_pct, improvement_priorities, program_grade, reference_version, wolfsberg_note), which is genuinely helpful. However, for a scoring tool whose entire substance is the decision inputs, the total silence on what `policy_parameters` should contain leaves a real hole. Chain provenance and privacy handling are adequately covered.

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 baseline is 3, and the description adds little beyond restating what the schema already says about compute modes and parent_hashes/parent_tool_ids chaining. Critically, it never explains what belongs in the opaque `policy_parameters` object beyond 'inputs for this tool's decision function' and 'unknown keys are refused' — the one place where prose could have compensated is left opaque.

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 names a specific verb and resource — scoring sanctions screening-program quality across list coverage, match calibration, alert tuning, escalation workflow and model validation into a composite program-conformance grade. That is clearly distinct from siblings like check_screening_list_coverage or score_fuzzy_match_calibration, though the differentiation is implicit in the component list rather than stated. The main weakness is placement: the actual purpose sits behind a wall of OpenChainGraph boilerplate.

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 only implied via chain position: it declares upstream artifacts (art-92-screening-list-coverage-checker, art-93-fuzzy-match-calibration-scorer) and a downstream consumer (cry-05-agent-action-audit-trail-aggregator), which tells an agent roughly where this fits. There is no explicit when-to-use versus when-not, and no routing to alternatives such as run_sanctions_screening_fit or build_sanctions_screening_evidence_pack, which an agent must choose between. The only directive given, 'Use synthetic or anonymised inputs only', is a constraint rather than guidance.

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.