X1 Wealth

Capital Call Job State

get_capital_call_job_state

Read-onlyIdempotent

Read the existing capital-call job tied to one exact document in your own X1 Vault. X1 returns whether household review is still needed, a confirmed obligation is waiting, the household reported it funded or no longer due, or the relation is held. This is a read-only administrative status, never authority to move money or proof of settlement.

Input Schema

Name	Required	Description	Default
`documentId`	Yes	Exact document ID returned by X1.

Output Schema

Name	Required	Description	Default
`facts`	Yes
`holds`	Yes
`state`	Yes
`source`	Yes
`closeout`	Yes
`contract`	Yes
`authority`	Yes
`eventKind`	Yes
`nextAction`	Yes
`obligation`	Yes
`projectedAt`	Yes
`firstPartyUrl`	Yes
`writesPerformed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

changedOutput schema / properties / closeout / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "id": {
-        "pattern": "^cc(?:ob|cl)_[a-f0-9]{32}$",
-        "type": "string"
-      },
-      "outcome": {
-        "enum": [
-          "funded",
-          "no_longer_due"
-        ],
-        "type": "string"
-      },
-      "reportedAt": {
-        "format": "date-time",
-        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "outcome",
-      "reportedAt"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "pattern": "^cc(?:ob|cl)_[a-f0-9]{32}$",
+        "type": "string"
+      },
+      "outcome": {
+        "enum": [
+          "funded",
+          "no_longer_due"
+        ],
+        "type": "string"
+      },
+      "reportedAt": {
+        "format": "date-time",
+        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "outcome",
+      "reportedAt"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / projectedAt / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"

First observedOct 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description earns credit for adding the enumerated state space (review needed, confirmed obligation waiting, funded, no longer due, held) and the explicit caveat that this is never authority to move money or proof of settlement. That caveat is real behavioral context an agent could not derive from the annotations.

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?

Three tight sentences, front-loaded with what it reads and scoped by document. The state enumeration is a long clause but carries genuine information; the only mild redundancy is restating scope and safety in sentence three.

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?

Output schema exists and annotations carry the safety profile, so the description need not explain return shapes. It covers purpose, scope and a critical non-authority caveat; only sibling differentiation is missing for a tool that sits beside two other capital-call readers.

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?

Single parameter with 100% schema coverage, including min/max length and 'Exact document ID returned by X1'. The description reinforces exactness ('one exact document') but adds no format or sourcing detail beyond the schema, so 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?

Specific verb (read) plus resource (capital-call job state) plus scope (one exact document in your own X1 Vault). It distinguishes itself from general list/search tools, but never names near-identical siblings like get_capital_call_source_state or get_capital_call_continuity, so an agent must infer the split.

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 implied — you check this when you have a single document and want to know where its capital-call job stands. There is no explicit when-not guidance and no mention of the two sibling capital-call tools, so choosing among them is left to inference.

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

All X1 Wealth tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.