Skip to main content
Glama

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "documentId": "<documentId>"
    },
    "name": "get_capital_call_job_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentIdYesExact document ID returned by X1.

Output Schema

NameRequiredDescriptionDefault
factsYes
holdsYes
stateYes
sourceYes
closeoutYes
contractYes
authorityYes
eventKindYes
nextActionYes
obligationYes
projectedAtYes
firstPartyUrlYes
writesPerformedYes
requestedDocumentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / nextAction / oneOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "code": {
      -        "const": "review_and_confirm_in_x1",
      -        "type": "string"
      -      },
      -      "display": {
      -        "const": "Ask the household owner to review and confirm this obligation in first-party X1.",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "code",
      -      "display"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "code": {
      -        "const": "wait_for_household_closeout",
      -        "type": "string"
      -      },
      -      "display": {
      -        "const": "Keep this job waiting. The household can close it out in first-party X1.",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "code",
      -      "display"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "code": {
      -        "const": "reuse_household_reported_result",
      -        "type": "string"
      -      },
      -      "display": {
      -        "const": "Reuse this household-reported result as prior X1 context. Do not claim settlement was verified.",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "code",
      -      "display"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "code": {
      -        "const": "inspect_capital_call_in_x1",
      -        "type": "string"
      -      },
      -      "display": {
      -        "const": "Review this capital-call record in first-party X1 before continuing.",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "code",
      -      "display"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "code": {
      +        "const": "review_and_confirm_in_x1",
      +        "type": "string"
      +      },
      +      "display": {
      +        "const": "Ask the household owner to review and confirm this obligation in first-party X1.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "code",
      +      "display"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "code": {
      +        "const": "review_x1_opened_call_in_x1",
      +        "type": "string"
      +      },
      +      "display": {
      +        "const": "X1 opened this call from the household's notice. Ask the household owner to review it in first-party X1.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "code",
      +      "display"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "code": {
      +        "const": "wait_for_household_closeout",
      +        "type": "string"
      +      },
      +      "display": {
      +        "const": "Keep this job waiting. The household can close it out in first-party X1.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "code",
      +      "display"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "code": {
      +        "const": "reuse_household_reported_result",
      +        "type": "string"
      +      },
      +      "display": {
      +        "const": "Reuse this household-reported result as prior X1 context. Do not claim settlement was verified.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "code",
      +      "display"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "code": {
      +        "const": "inspect_capital_call_in_x1",
      +        "type": "string"
      +      },
      +      "display": {
      +        "const": "Review this capital-call record in first-party X1 before continuing.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "code",
      +      "display"
      +    ],
      +    "type": "object"
      +  }
      +]
    • addedOutput schema / properties / requestedDocumentId
      Added value: +{
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedOutput schema / properties / state / enum
      Previous value: -[
      -  "awaiting_household_confirmation",
      -  "confirmed_waiting",
      -  "held",
      -  "household_reported_funded",
      -  "household_reported_no_longer_due"
      -]New value: +[
      +  "awaiting_household_confirmation",
      +  "confirmed_waiting",
      +  "held",
      +  "household_reported_funded",
      +  "household_reported_no_longer_due",
      +  "x1_opened_waiting"
      +]
  2. Changed2 schema fields changed
    • 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))$"
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context by listing the possible status outcomes and explicitly stating this is 'never authority to move money or proof of settlement,' though it does not discuss error cases or permissions.

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

Conciseness5/5

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

The description is three tight sentences: purpose first, returned state categories second, and an important semantic caveat last. It is front-loaded and contains no wasted wording.

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?

Given one required parameter, rich annotations, and an output schema, the description supplies enough context for safe invocation. It explains the administrative nature and limits of the returned status without needing to duplicate schema or output details.

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%, and the single documentId parameter is fully documented in the schema. The description reinforces that it must be one exact document but adds no meaningful parameter semantics beyond the schema, so the 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 description states a specific verb and resource: reading the existing capital-call job tied to one exact document. Scope is clear, but it does not explicitly distinguish this from sibling tools such as get_capital_call_continuity or get_capital_call_source_state, so it falls short of a 5.

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?

The phrase 'tied to one exact document in your own X1 Vault' gives implied usage context, but the description does not explicitly say when to use this tool versus the other capital-call siblings or when not to use it. Guidance is therefore present but mostly inferred.

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.