Skip to main content
Glama

Ariadne Nexus Quantitative Engine

by com.ariadnenexus
OverviewDiscussionsAdmin

Weekly Sovereign Macro-Prudential & Sanctions Policy Monitor

get_sovereign_policy_brief
Read-onlyIdempotent

Generates the Weekly Sovereign Macro-Prudential & Sanctions Monitor for Federal Reserve (FOMC / Financial Stability), U.S. Treasury (OFR / OFAC / FinCEN), and SEC DERA policy desks, combining Dual-Track monetary stability indicators (10Y-3M yield curve inversion, FINRA TRACE G-SIB credit spread dislocations, H.8 bank credit impulse) and autonomous x402 sanctions enforcement telemetry. Use when: synthesizing macro-prudential systemic risk briefings, monitoring aggregate sanctions enforcement trends, or evaluating FAR Subpart 13.2 ($9,500 GPC Micro-Purchase) policy data procurement options. Do not use when: screening a specific individual or corporate counterparty against the OFAC SDN list (use screen_ofac_entity instead), or drafting a formal APA 5 U.S.C. § 553 public comment letter for a specific agency rulemaking docket (use synthesize_regulatory_docket instead). Behavior: Read-only, deterministic intelligence report generator ($1.00 USD per call via apiKey or paymentToken; returns an x402/MPP paymentChallenge without charging if credentials are omitted).

Input Schema

NameRequiredDescriptionDefault
apiKeyNoOptional Ariadne Nexus Developer API key ("nexus_live_...") for authenticated execution. May also be passed via the x-api-key HTTP header.
paymentTokenNoOptional Stripe Shared Payment Token ("spt_...") or settled x402 payment receipt hash ("rcpt_...") for pay-per-call execution ($1.00 USD).
include_markdownNoWhen true, includes the complete publication-ready Markdown policy brief in markdown_body alongside structured JSON telemetry (default: true).

Output Schema

NameRequiredDescriptionDefault
toolYesExecuted tool identifier ("get_sovereign_policy_brief").
titleYesFormal policy brief title.
receiptNoCryptographic payment or API key settlement receipt ID.
brief_idYesUnique weekly policy brief identifier.
snapshotNoUnderlying quantitative macro and sanctions telemetry snapshot.
subtitleNoTarget regulatory desk subtitle.
generated_atNoISO-8601 generation timestamp.
markdown_bodyNoFull formatted Markdown policy brief (present when include_markdown is true).
reporting_weekNoISO reporting week label.
cadence_scheduleNoPublication cadence schedule.
executive_summaryYesHigh-level macro-prudential and illicit-finance synthesis.
policy_directivesYesActionable regulatory policy recommendations.
procurement_optionsNoFAR Subpart 13.2 ($9,500 GPC Micro-Purchase) and x402 procurement channels.
monetary_track_findingsYesTrack 1 Federal Reserve / OFR monetary and credit liquidity findings.
illicit_finance_track_findingsYesTrack 2 Treasury FinCEN / OFAC autonomous x402 sanctions findings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / apiKey / description
      Previous value: -"Optional Ariadne Developer API key (nexus_live_...)"New value: +"Optional Ariadne Nexus Developer API key (\"nexus_live_...\") for authenticated execution. May also be passed via the x-api-key HTTP header."
    • changedInput schema / properties / include_markdown / description
      Previous value: -"Include full markdown brief body (default: true)"New value: +"When true, includes the complete publication-ready Markdown policy brief in markdown_body alongside structured JSON telemetry (default: true)."
    • changedInput schema / properties / paymentToken / description
      Previous value: -"Optional Stripe Shared Payment Token (spt_...) or x402 receipt"New value: +"Optional Stripe Shared Payment Token (\"spt_...\") or settled x402 payment receipt hash (\"rcpt_...\") for pay-per-call execution ($1.00 USD)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "brief_id": {
+      "description": "Unique weekly policy brief identifier.",
+      "type": "string"
+    },
+    "cadence_schedule": {
+      "description": "Publication cadence schedule.",
+      "type": "string"
+    },
+    "executive_summary": {
+      "description": "High-level macro-prudential and illicit-finance synthesis.",
+      "type": "string"
+    },
+    "generated_at": {
+      "description": "ISO-8601 generation timestamp.",
+      "type": "string"
+    },
+    "illicit_finance_track_findings": {
+      "description": "Track 2 Treasury FinCEN / OFAC autonomous x402 sanctions findings.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "markdown_body": {
+      "description": "Full formatted Markdown policy brief (present when include_markdown is true).",
+      "type": "string"
+    },
+    "monetary_track_findings": {
+      "description": "Track 1 Federal Reserve / OFR monetary and credit liquidity findings.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "policy_directives": {
+      "description": "Actionable regulatory policy recommendations.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "procurement_options": {
+      "description": "FAR Subpart 13.2 ($9,500 GPC Micro-Purchase) and x402 procurement channels.",
+      "type": "object"
+    },
+    "receipt": {
+      "description": "Cryptographic payment or API key settlement receipt ID.",
+      "type": "string"
+    },
+    "reporting_week": {
+      "description": "ISO reporting week label.",
+      "type": "string"
+    },
+    "snapshot": {
+      "description": "Underlying quantitative macro and sanctions telemetry snapshot.",
+      "type": "object"
+    },
+    "subtitle": {
+      "description": "Target regulatory desk subtitle.",
+      "type": "string"
+    },
+    "title": {
+      "description": "Formal policy brief title.",
+      "type": "string"
+    },
+    "tool": {
+      "description": "Executed tool identifier (\"get_sovereign_policy_brief\").",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "brief_id",
+    "title",
+    "executive_summary",
+    "monetary_track_findings",
+    "illicit_finance_track_findings",
+    "policy_directives"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/destructive status, and the description adds material context beyond them: it is deterministic, costs $1.00 USD per call, and returns an x402/MPP paymentChallenge without charging when credentials are omitted. That payment-and-credential behavior is not derivable from the annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the report identity, then cleanly structured as Use-when / Do-not-use-when / Behavior blocks. The prose is dense with domain jargon and repeats the title verbatim, which slightly inflates length, but every clause carries routing or behavioral information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return formatting need not be documented, and the description nonetheless points to markdown_body plus structured telemetry. Combined with the usage exclusions and payment semantics, an agent has everything needed to call this correctly.

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 description coverage is 100%, so the baseline is 3, but the description adds real semantics: it clarifies that apiKey and paymentToken are the two credential paths and explains the no-credential fallback behavior. It does not, however, explain include_markdown's effect beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (generates) and a concrete resource (Weekly Sovereign Macro-Prudential & Sanctions Monitor), and explicitly names the target desks and indicator set it synthesizes. It also differentiates itself from siblings in the same paragraph rather than leaving the agent to compare schemas.

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

Usage Guidelines5/5

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

Contains explicit 'Use when:' triggers and 'Do not use when:' exclusions, each routing to a named sibling (screen_ofac_entity for counterparty screening, synthesize_regulatory_docket for comment letters). This is the strongest possible routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ariadne Nexus Quantitative Engine toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources