Skip to main content
Glama

AINumbers Fintech Intelligence Suite

Arc Partner Stablecoin Onboarding Conformance

score_partner_stablecoin_readiness
Read-onlyIdempotent

Arc Partner Stablecoin Onboarding Conformance: 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. Consumes upstream artifacts from: art-42-arc-fit-diagnostic. Output feeds: art-45-arc-xreserve-linter. Open at: https://ainumbers.co/chaingraph/art-110-arc-partner-stablecoin-onboarding.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: Score a non-USD stablecoin issuer readiness to join Circle Partner Stablecoins on Arc against technical/operational, reserve-management, and risk-management standards. Outputs: ccy, composite_grade, eligible, gaps, grade, home_regime, reserve_score, risk_score, tech_score, verdict. Output schema: call describe_tool("score_partner_stablecoin_readiness").

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

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: issuer_profile. 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: issuer_profile. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "issuer_profile": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "ccy": {
      -      "type": "string"
      -    },
      -    "composite_grade": {
      -      "type": "integer"
      -    },
      -    "eligible": {
      -      "type": "boolean"
      -    },
      -    "gaps": {
      -      "type": "array"
      -    },
      -    "grade": {
      -      "type": "string"
      -    },
      -    "home_regime": {
      -      "type": "string"
      -    },
      -    "reserve_score": {
      -      "type": "integer"
      -    },
      -    "risk_score": {
      -      "type": "integer"
      -    },
      -    "tech_score": {
      -      "type": "integer"
      -    },
      -    "verdict": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "ccy": {
      +      "type": "string"
      +    },
      +    "composite_grade": {
      +      "type": "integer"
      +    },
      +    "eligible": {
      +      "type": "boolean"
      +    },
      +    "gaps": {
      +      "type": "array"
      +    },
      +    "grade": {
      +      "type": "string"
      +    },
      +    "home_regime": {
      +      "type": "string"
      +    },
      +    "reserve_score": {
      +      "type": "integer"
      +    },
      +    "risk_score": {
      +      "type": "integer"
      +    },
      +    "tech_score": {
      +      "type": "integer"
      +    },
      +    "verdict": {
      +      "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?

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses that execution is deterministic, that compute:"auto" runs server-side on Cloudflare Workers for gpu:false nodes with a registered kernel while compute:"browser" returns a delegation URL instead, and that gpu:true always delegates. It also states inputs are processed transiently and not stored or logged, mandates synthetic/anonymised inputs, and notes an AP2 artifact with execution_hash is exported — all real behavioral context the annotations do not carry.

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 actionable content (what is scored, what comes out) is at the very end, behind compute-binding boilerplate, a chain-provenance narrative, a URL and a 64-character FV-status hash. Much of the block is generic OpenChainGraph runtime text that applies to every node rather than this tool, so the description is not front-loaded and does not earn all its length.

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?

It is fairly complete on runtime behavior, privacy, chaining and the ten output fields, which compensates for the absent output schema. But for a scoring tool whose only real input is a nested issuer_profile, the description gives no indication of what that profile must contain, leaving the most important call-shaping detail undocumented.

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 schema already documents compute, parent_hashes, parent_tool_ids and policy_parameters; the description's compute-mode explanation largely restates the schema. It adds no detail about the shape of issuer_profile, which is the one genuinely under-specified parameter (a nested object with no defined properties).

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 sentences give a specific verb and resource: score a non-USD stablecoin issuer's readiness to join Circle Partner Stablecoins on Arc against technical/operational, reserve-management and risk-management standards, plus a named output list. However, the purpose is buried after several sentences of chain/provenance boilerplate, and it never names a sibling (e.g. route_partner_stablecoin_jurisdiction, run_arc_fit_diagnostic, lint_arc_xreserve_config) to differentiate itself from.

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 is only implied through the chain position: it consumes art-42-arc-fit-diagnostic and feeds art-45-arc-xreserve-linter, which hints at where it sits in a workflow. There is no explicit when-to-use/when-not guidance and no statement about which sibling to pick for adjacent tasks such as jurisdiction routing or reserve-config linting.

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.