Skip to main content
Glama

AINumbers Fintech Intelligence Suite

Agent Identity & Authorization Attestation Checker

check_agent_attestation
Read-onlyIdempotent

Agent Identity & Authorization Attestation Checker: OpenChainGraph compute node (compliance_mandate). Regulatory deadline: 2027-12 (EU AI Act Annex III high-risk obligations (Digital Omnibus, Parliament final approval June 2026) push agent KYA toward compliance requirement from 2 December 2027; KYA-OS donated to DIF March 2026). 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-01-ap2-mandate-chain-validator, art-02-agent-spend-policy-simulator, art-13-eudi-wallet-credential-readiness-checker. Output feeds: art-02-agent-spend-policy-simulator, art-32-a2a-agent-card-trust-chain-validator, ptg-01-ap2-prompt-template-generator. Open at: https://ainumbers.co/chaingraph/art-04-agent-identity-attestation-checker.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: KYA-OS (DIF Trusted AI Agents WG) credential-chain attestation: delegated-authority credential chain, scope limits, validity windows (max 90 days), chain depth cap (4 hops), EU AI Act high-risk scope classification. Outputs: overall_status, pass, fail, warn, checks, root_agent_id, scopes. Output schema: call describe_tool("check_agent_attestation").

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

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: credential, validate_at_unix. 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: credential, validate_at_unix. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "credential": {},
      +  "validate_at_unix": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "checks": {
      -      "items": {
      -        "properties": {
      -          "code": {
      -            "type": "string"
      -          },
      -          "status": {
      -            "type": "string"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "fail": {
      -      "type": "integer"
      -    },
      -    "overall_status": {
      -      "type": "string"
      -    },
      -    "pass": {
      -      "type": "integer"
      -    },
      -    "root_agent_id": {
      -      "type": "string"
      -    },
      -    "scopes": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "warn": {
      -      "type": "integer"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checks": {
      +      "items": {
      +        "properties": {
      +          "code": {
      +            "type": "string"
      +          },
      +          "status": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "fail": {
      +      "type": "integer"
      +    },
      +    "overall_status": {
      +      "type": "string"
      +    },
      +    "pass": {
      +      "type": "integer"
      +    },
      +    "root_agent_id": {
      +      "type": "string"
      +    },
      +    "scopes": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "warn": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Changed3 schema fields changed
    • addedInput schema / properties / compute
      Added value: +{
      +  "description": "Compute 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.",
      +  "enum": [
      +    "auto",
      +    "server",
      +    "browser"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / inputs
      Removed value: -{
      -  "additionalProperties": {},
      -  "description": "Simulation parameters for this tool's input fields. See the tool's embedded manifest for field names.",
      -  "propertyNames": {
      -    "type": "string"
      -  },
      -  "type": "object"
      -}
    • addedInput schema / properties / policy_parameters
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "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.",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
  6. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/local-only, and the description goes meaningfully beyond them: inputs are processed transiently and not stored or logged, compute:'auto' runs server-side on Cloudflare Workers while compute:'browser' returns a browser delegation URL, gpu:true nodes always delegate, and the call exports an AP2 artifact with execution_hash for provenance. The FV-status snapshot note also explains offline receipt verification. Some of this is marketing boilerplate, but the delegation and retention behavior is genuinely additive.

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 payload is dominated by non-operational material: a regulatory-deadline digression about the Digital Omnibus and KYA-OS's DIF donation, a full FV-status file path with a 64-character hash, and upstream/downstream artifact ID lists. The single most useful sentence — what the tool actually checks — is buried at the very end, so the description is neither front-loaded nor economical.

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?

With no output schema, the description compensates by enumerating return fields (overall_status, pass, fail, warn, checks, root_agent_id, scopes) and by spelling out the substantive checks (scope limits, validity window, depth cap, high-risk scope classification). The chain-provenance inputs are also explained. Only the expected credential format for policy_parameters.credential is left unspecified.

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 both compute modes and the parent_hashes/parent_tool_ids chaining contract are already documented in structured fields. The description restates the compute:'auto'/'browser' semantics and the policy_parameters requirement ('credential, validate_at_unix') rather than adding format or validation detail beyond the schema. Baseline 3 applies.

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 final summary sentence names a specific verb and resource: KYA-OS credential-chain attestation covering delegated-authority chains, scope limits, 90-day validity windows, 4-hop depth cap, and EU AI Act high-risk scope classification. That is far more specific than the title. However, it never distinguishes itself from close siblings such as verify_acdc_delegation_chain, validate_a2a_trust_chain, or check_agent_token_scope, so an agent must infer which chain-checking tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not-to-use guidance and no named alternative. The only imperative is an input constraint ('Use synthetic or anonymised inputs only'). The regulatory-deadline paragraph establishes domain context (EU AI Act high-risk from Dec 2027) but does not tell the agent under what circumstances to select this tool over a sibling.

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.