Skip to main content
Glama

AINumbers Fintech Intelligence Suite

Swift CSP Assessor Independence Eligibility

check_assessor_independence
Read-onlyIdempotent

Swift CSP Assessor Independence Eligibility: 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-487-assessor-independence-check.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: Checks eligibility of a Swift CSCF Independent Assessment Framework assessment: assessment route (internal 2nd/3rd line vs external) against a policy-supplied permitted-routes-per-architecture-type table, claimed assessor certifications against a policy-supplied required set, an independence-from... Outputs: architecture_type, assessment_date, assessment_route, attestation_deadline, cert_eligible, date_eligible, eligible, failing_predicate, independence_eligible, overlapping_identities, route_eligible. Output schema: call describe_tool("check_assessor_independence").

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

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: architecture_type, assessment_date, assessment_route, assessor_person_ids, attestation_deadline, claimed_assessor_certifications, identity_set, implementer_person_ids, permitted_routes, required_certifications. 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: architecture_type, assessment_date, assessment_route, assessor_person_ids, attestation_deadline, claimed_assessor_certifications, identity_set, implementer_person_ids, permitted_routes, required_certifications. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "architecture_type": {},
      +  "assessment_date": {},
      +  "assessment_route": {},
      +  "assessor_person_ids": {},
      +  "attestation_deadline": {},
      +  "claimed_assessor_certifications": {},
      +  "identity_set": {
      +    "type": "array"
      +  },
      +  "implementer_person_ids": {},
      +  "permitted_routes": {
      +    "type": "array"
      +  },
      +  "required_certifications": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "architecture_type": {
      -      "type": "string"
      -    },
      -    "assessment_date": {
      -      "type": "string"
      -    },
      -    "assessment_route": {
      -      "type": "string"
      -    },
      -    "attestation_deadline": {
      -      "type": "string"
      -    },
      -    "cert_eligible": {
      -      "type": "boolean"
      -    },
      -    "date_eligible": {
      -      "type": "boolean"
      -    },
      -    "eligible": {
      -      "type": "boolean"
      -    },
      -    "failing_predicate": {
      -      "type": "string"
      -    },
      -    "independence_eligible": {
      -      "type": "boolean"
      -    },
      -    "overlapping_identities": {
      -      "type": "array"
      -    },
      -    "route_eligible": {
      -      "type": "boolean"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "architecture_type": {
      +      "type": "string"
      +    },
      +    "assessment_date": {
      +      "type": "string"
      +    },
      +    "assessment_route": {
      +      "type": "string"
      +    },
      +    "attestation_deadline": {
      +      "type": "string"
      +    },
      +    "cert_eligible": {
      +      "type": "boolean"
      +    },
      +    "date_eligible": {
      +      "type": "boolean"
      +    },
      +    "eligible": {
      +      "type": "boolean"
      +    },
      +    "failing_predicate": {
      +      "type": "string"
      +    },
      +    "independence_eligible": {
      +      "type": "boolean"
      +    },
      +    "overlapping_identities": {
      +      "type": "array"
      +    },
      +    "route_eligible": {
      +      "type": "boolean"
      +    }
      +  },
      +  "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 and non-destructive, so the safety bar is low; the description nonetheless adds substantive behavior: default server-side execution on Workers, browser delegation for compute:"browser" or gpu:true nodes, transient non-retention of inputs, and an AP2 artifact export carrying execution_hash. What it omits is what a failing result means operationally (only the failing_predicate output name hints at it).

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 actual purpose statement is buried after a large block of infrastructure boilerplate (compute binding, Cloudflare Workers, privacy policy, AP2 export, an FV-status URL and hash) and the one sentence that matters is truncated with an ellipsis. Roughly half the text is platform-level copy duplicated across every node in this server rather than information about this tool.

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?

Return values are enumerated (eligible, route_eligible, cert_eligible, independence_eligible, date_eligible, failing_predicate, overlapping_identities), which compensates for the missing output schema, and the compute/privacy behavior is fully covered. What is missing is the decision logic itself: which conditions cause which predicate to fail, how assessment_date is validated against attestation_deadline, and how overlapping_identities is derived.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the permitted_routes field is a policy-supplied table keyed by architecture_type, and required_certifications is a policy-supplied required set compared against claimed_assessor_certifications. That explains intent of the nested policy_parameters block beyond the property names, though individual field formats (date, route enums) remain undocumented in prose.

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: it checks eligibility of a Swift CSCF Independent Assessment Framework assessment across route, certification and independence predicates. The clause is truncated mid-way ("independence-from..."), so the third predicate is never actually named, and no sibling (e.g. check_cscf_control_applicability) is distinguished, but the core operation is still identifiable.

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 no explicit when-to-use / when-not-to-use statement and no named alternative among the many Swift/NIS2/CSCF siblings. The only real usage constraint given is "Use synthetic or anonymised inputs only" plus the compute-mode guidance, which implies a policy-configured compliance evaluation rather than stating selection criteria.

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.