Skip to main content
Glama

AINumbers Fintech Intelligence Suite

AIUC-1 Control Evidence Linter

lint_aiuc1_control_evidence
Read-onlyIdempotent

AIUC-1 Control Evidence Linter: 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. Output feeds: art-304-aiuc1-evidence-pack-assembler. Open at: https://ainumbers.co/chaingraph/art-303-aiuc1-control-evidence-linter.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: Lints a supplied control-evidence bundle against the 23 automatable AIUC-1 v2026-Q1 controls (pillars A-F): version-guards the catalog, classifies each automatable control receipt-backed, attestation-only, or missing, and reports per-pillar and overall coverage. Outputs: aiuc1_version, attestation_only_count, automatable_scope, insufficient_evidence, missing_count, overall_coverage, per_control, per_pillar_coverage, procedural_controls_out_of_scope, receipt_backed_count, version_mismatch. Output schema: call describe_tool("lint_aiuc1_control_evidence").

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

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: aiuc1_version, control_evidence. 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: aiuc1_version, control_evidence. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "aiuc1_version": {},
      +  "control_evidence": {
      +    "type": "array"
      +  }
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "aiuc1_version": {
      -      "type": "string"
      -    },
      -    "attestation_only_count": {
      -      "type": "integer"
      -    },
      -    "automatable_scope": {
      -      "type": "integer"
      -    },
      -    "insufficient_evidence": {
      -      "type": "boolean"
      -    },
      -    "missing_count": {
      -      "type": "integer"
      -    },
      -    "overall_coverage": {
      -      "type": "integer"
      -    },
      -    "per_control": {
      -      "items": {
      -        "properties": {
      -          "control_id": {
      -            "type": "string"
      -          },
      -          "pillar": {
      -            "type": "string"
      -          },
      -          "status": {
      -            "type": "string"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "per_pillar_coverage": {
      -      "properties": {
      -        "A": {
      -          "type": "integer"
      -        },
      -        "B": {
      -          "type": "integer"
      -        },
      -        "C": {
      -          "type": "integer"
      -        },
      -        "D": {
      -          "type": "integer"
      -        },
      -        "E": {
      -          "type": "integer"
      -        },
      -        "F": {
      -          "type": "integer"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "procedural_controls_out_of_scope": {
      -      "type": "integer"
      -    },
      -    "receipt_backed_count": {
      -      "type": "integer"
      -    },
      -    "version_mismatch": {
      -      "type": "boolean"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "aiuc1_version": {
      +      "type": "string"
      +    },
      +    "attestation_only_count": {
      +      "type": "integer"
      +    },
      +    "automatable_scope": {
      +      "type": "integer"
      +    },
      +    "insufficient_evidence": {
      +      "type": "boolean"
      +    },
      +    "missing_count": {
      +      "type": "integer"
      +    },
      +    "overall_coverage": {
      +      "type": "integer"
      +    },
      +    "per_control": {
      +      "items": {
      +        "properties": {
      +          "control_id": {
      +            "type": "string"
      +          },
      +          "pillar": {
      +            "type": "string"
      +          },
      +          "status": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "per_pillar_coverage": {
      +      "properties": {
      +        "A": {
      +          "type": "integer"
      +        },
      +        "B": {
      +          "type": "integer"
      +        },
      +        "C": {
      +          "type": "integer"
      +        },
      +        "D": {
      +          "type": "integer"
      +        },
      +        "E": {
      +          "type": "integer"
      +        },
      +        "F": {
      +          "type": "integer"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "procedural_controls_out_of_scope": {
      +      "type": "integer"
      +    },
      +    "receipt_backed_count": {
      +      "type": "integer"
      +    },
      +    "version_mismatch": {
      +      "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, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: deterministic execution, server-vs-browser compute modes, transient processing with no storage or logging, an AP2 artifact export carrying execution_hash, and catalog version-guarding. It falls short of a 5 only because the return-shape description is a bare field list and pagination/error behavior is unaddressed.

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 text is dominated by repeated boilerplate (compute binding, transient-processing notice, 'Summary:' restatement), a raw documentation URL, and a full FV-status SHA-256 hash that consumes space without helping an agent invoke the tool. Critically, the structure is back-loaded: the actual purpose and output list sit at the end, behind material that applies to every node in this family.

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?

Given a nested policy_parameters object and no output schema, the description does the necessary work by enumerating the returned fields (aiuc1_version, attestation_only_count, per_pillar_coverage, receipt_backed_count, version_mismatch, and so on). Combined with the required-input and version-guard notes, an agent has enough to call it correctly, though it defers the full schema to describe_tool rather than explaining it inline.

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. The description adds some meaning by naming the required policy_parameters keys (aiuc1_version, control_evidence) and explaining the version-guard behavior, but parent_hashes and parent_tool_ids — the chaining mechanism — get no treatment in the description at all. Overall it neither compensates for nor degrades what the schema already documents.

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 description eventually states a specific verb and resource: it lints a supplied control-evidence bundle against the 23 automatable AIUC-1 v2026-Q1 controls (pillars A-F) and classifies each as receipt-backed, attestation-only, or missing. However, that purpose appears only after ~70% of boilerplate about compute nodes, privacy, and provenance, so an agent skimming the opening lines would see a linter name and generic compute-node text rather than the actual function. Sibling differentiation is only implicit via the 'Output feeds: art-304-aiuc1-evidence-pack-assembler' pipeline note.

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 implied by the pipeline statement that output feeds the evidence-pack assembler, which tells an agent this is the pre-assembly lint step. There is one concrete constraint ('Use synthetic or anonymised inputs only') but no explicit when-to-use versus alternatives, and no mention of siblings like check_etr_control_evidence or assemble_aiuc1_evidence_pack that an agent might confuse it with. The 'Required: aiuc1_version, control_evidence' line is the closest thing to a precondition.

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.