Skip to main content
Glama

X1 Wealth

by com.x1wealth
OverviewDiscussionsAdmin

X1 Workflow Guide

get_x1_workflow_guide
Read-onlyIdempotent

Get role-aware guidance: keep_and_continue for keeping useful financial work, resuming it later, or understanding a new source or reply; financial_workbench for analysis, document comparisons, scenarios, and briefs; use money_check for dated official state unclaimed-property destinations, not search results. Or choose an X1 workflow artifact: communications thread, packet, missing-document request, decision log, saved artifact, professional intro, or app navigation, with full production app URLs.

Input Schema

NameRequiredDescriptionDefault
topicNoOptional user-facing topic or objective, such as tax strategy, estate update, insurance review, missing K-1, or intro to CPA.
detailNoReturn concise guidance by default, or detailed decision rules.
statesNoFor money_check only: US state or DC codes the person wants to check, such as CA and FL. Returns official destinations, not search results. Omit to choose states in X1.
clientIdNoAuthorized client/member ID when already known. If unknown, start from roster/search tools first.
workflowNoWorkflow to plan. Use keep_and_continue when the person wants to keep useful financial work for later, resume earlier work, or understand what a new source or reply changes. Use financial_workbench for broad financial questions, document comparisons, scenarios, briefs, or household overviews. Use review_capital_call only for a capital-call notice, preserving the person's original situation in topic even if they just connected X1. Use property_management for adding a home or investment condo or updating its value; mortgage_setup for connecting a lender or uploading a mortgage statement; loan_management for entering or maintaining an SBA, business, personal or other manual loan; money_check for official state unclaimed-property search guidance; human_support for a product error. Other workflows include account_setup, connection_recovery, coordinate_with_team, and document_review.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / workflow / description
      Previous value: -"Workflow to plan. Use financial_workbench for broad financial questions, document comparisons, scenarios, briefs, or household overviews. Use review_capital_call only for a capital-call notice, preserving the person's original situation in topic even if they just connected X1. Use property_management for adding a home or investment condo or updating its value; mortgage_setup for connecting a lender or uploading a mortgage statement; loan_management for entering or maintaining an SBA, business, personal or other manual loan; money_check for official state unclaimed-property search guidance; human_support for a product error. Other workflows include account_setup, connection_recovery, coordinate_with_team, and document_review."New value: +"Workflow to plan. Use keep_and_continue when the person wants to keep useful financial work for later, resume earlier work, or understand what a new source or reply changes. Use financial_workbench for broad financial questions, document comparisons, scenarios, briefs, or household overviews. Use review_capital_call only for a capital-call notice, preserving the person's original situation in topic even if they just connected X1. Use property_management for adding a home or investment condo or updating its value; mortgage_setup for connecting a lender or uploading a mortgage statement; loan_management for entering or maintaining an SBA, business, personal or other manual loan; money_check for official state unclaimed-property search guidance; human_support for a product error. Other workflows include account_setup, connection_recovery, coordinate_with_team, and document_review."
    • changedInput schema / properties / workflow / enum
      Previous value: -[
-  "financial_workbench",
-  "answer_what_can_x1_do",
-  "account_setup",
-  "review_capital_call",
-  "property_management",
-  "mortgage_setup",
-  "loan_management",
-  "money_check",
-  "connection_recovery",
-  "human_support",
-  "prepare_meeting",
-  "coordinate_with_team",
-  "review_communications",
-  "start_communications_thread",
-  "request_missing_document",
-  "create_packet",
-  "log_decision",
-  "save_note_or_artifact",
-  "specialist_support",
-  "professional_intro",
-  "document_review",
-  "network_professional_shared_work"
-]New value: +[
+  "financial_workbench",
+  "keep_and_continue",
+  "answer_what_can_x1_do",
+  "account_setup",
+  "review_capital_call",
+  "property_management",
+  "mortgage_setup",
+  "loan_management",
+  "money_check",
+  "connection_recovery",
+  "human_support",
+  "prepare_meeting",
+  "coordinate_with_team",
+  "review_communications",
+  "start_communications_thread",
+  "request_missing_document",
+  "create_packet",
+  "log_decision",
+  "save_note_or_artifact",
+  "specialist_support",
+  "professional_intro",
+  "document_review",
+  "network_professional_shared_work"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / states
      Added value: +{
+  "description": "For money_check only: US state or DC codes the person wants to check, such as CA and FL. Returns official destinations, not search results. Omit to choose states in X1.",
+  "items": {
+    "enum": [
+      "AL",
+      "AK",
+      "AZ",
+      "AR",
+      "CA",
+      "CO",
+      "CT",
+      "DE",
+      "DC",
+      "FL",
+      "GA",
+      "HI",
+      "ID",
+      "IL",
+      "IN",
+      "IA",
+      "KS",
+      "KY",
+      "LA",
+      "ME",
+      "MD",
+      "MA",
+      "MI",
+      "MN",
+      "MS",
+      "MO",
+      "MT",
+      "NE",
+      "NV",
+      "NH",
+      "NJ",
+      "NM",
+      "NY",
+      "NC",
+      "ND",
+      "OH",
+      "OK",
+      "OR",
+      "PA",
+      "RI",
+      "SC",
+      "SD",
+      "TN",
+      "TX",
+      "UT",
+      "VT",
+      "VA",
+      "WA",
+      "WV",
+      "WI",
+      "WY"
+    ],
+    "type": "string"
+  },
+  "maxItems": 51,
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / properties / workflow / description
      Previous value: -"Workflow to plan. Use financial_workbench for broad financial questions, document comparisons, scenarios, briefs, or household overviews. Use review_capital_call only for a capital-call notice, preserving the person's original situation in topic even if they just connected X1. Use property_management for adding a home or investment condo or updating its value; mortgage_setup for connecting a lender or uploading a mortgage statement; loan_management for entering or maintaining an SBA, business, personal or other manual loan; human_support for a product error. Other workflows include account_setup, connection_recovery, coordinate_with_team, and document_review."New value: +"Workflow to plan. Use financial_workbench for broad financial questions, document comparisons, scenarios, briefs, or household overviews. Use review_capital_call only for a capital-call notice, preserving the person's original situation in topic even if they just connected X1. Use property_management for adding a home or investment condo or updating its value; mortgage_setup for connecting a lender or uploading a mortgage statement; loan_management for entering or maintaining an SBA, business, personal or other manual loan; money_check for official state unclaimed-property search guidance; human_support for a product error. Other workflows include account_setup, connection_recovery, coordinate_with_team, and document_review."
    • changedInput schema / properties / workflow / enum
      Previous value: -[
-  "financial_workbench",
-  "answer_what_can_x1_do",
-  "account_setup",
-  "review_capital_call",
-  "property_management",
-  "mortgage_setup",
-  "loan_management",
-  "connection_recovery",
-  "human_support",
-  "prepare_meeting",
-  "coordinate_with_team",
-  "review_communications",
-  "start_communications_thread",
-  "request_missing_document",
-  "create_packet",
-  "log_decision",
-  "save_note_or_artifact",
-  "specialist_support",
-  "professional_intro",
-  "document_review",
-  "network_professional_shared_work"
-]New value: +[
+  "financial_workbench",
+  "answer_what_can_x1_do",
+  "account_setup",
+  "review_capital_call",
+  "property_management",
+  "mortgage_setup",
+  "loan_management",
+  "money_check",
+  "connection_recovery",
+  "human_support",
+  "prepare_meeting",
+  "coordinate_with_team",
+  "review_communications",
+  "start_communications_thread",
+  "request_missing_document",
+  "create_packet",
+  "log_decision",
+  "save_note_or_artifact",
+  "specialist_support",
+  "professional_intro",
+  "document_review",
+  "network_professional_shared_work"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / workflow / description
      Previous value: -"Workflow to plan. Use financial_workbench for broad financial questions, document comparisons, scenarios, briefs, or household overviews. Use review_capital_call only for a capital-call notice, preserving the person's original situation in topic even if they just connected X1. Use property_management for adding a home or investment condo or updating its value; mortgage_setup for connecting a lender or uploading a mortgage statement; human_support for a product error. Other workflows include account_setup, connection_recovery, coordinate_with_team, and document_review."New value: +"Workflow to plan. Use financial_workbench for broad financial questions, document comparisons, scenarios, briefs, or household overviews. Use review_capital_call only for a capital-call notice, preserving the person's original situation in topic even if they just connected X1. Use property_management for adding a home or investment condo or updating its value; mortgage_setup for connecting a lender or uploading a mortgage statement; loan_management for entering or maintaining an SBA, business, personal or other manual loan; human_support for a product error. Other workflows include account_setup, connection_recovery, coordinate_with_team, and document_review."
    • changedInput schema / properties / workflow / enum
      Previous value: -[
-  "financial_workbench",
-  "answer_what_can_x1_do",
-  "account_setup",
-  "review_capital_call",
-  "property_management",
-  "mortgage_setup",
-  "connection_recovery",
-  "human_support",
-  "prepare_meeting",
-  "coordinate_with_team",
-  "review_communications",
-  "start_communications_thread",
-  "request_missing_document",
-  "create_packet",
-  "log_decision",
-  "save_note_or_artifact",
-  "specialist_support",
-  "professional_intro",
-  "document_review",
-  "network_professional_shared_work"
-]New value: +[
+  "financial_workbench",
+  "answer_what_can_x1_do",
+  "account_setup",
+  "review_capital_call",
+  "property_management",
+  "mortgage_setup",
+  "loan_management",
+  "connection_recovery",
+  "human_support",
+  "prepare_meeting",
+  "coordinate_with_team",
+  "review_communications",
+  "start_communications_thread",
+  "request_missing_document",
+  "create_packet",
+  "log_decision",
+  "save_note_or_artifact",
+  "specialist_support",
+  "professional_intro",
+  "document_review",
+  "network_professional_shared_work"
+]
  4. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds one useful output fact—'full production app URLs'—and the role-aware framing, but says nothing about guidance format, length, or how detail=concise/detailed changes the result.

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?

A single rambling run-on sentence crams the entire workflow taxonomy into one breath, with 'Or choose an X1 workflow artifact...' bolted on. It is dense and hard to parse rather than front-loaded and structured.

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?

For a zero-required-parameter guide with no output schema, the description conveys the broad domain and output contains app URLs, which is adequate. But with 5 parameters and a lookalike sibling, it stops short of telling the agent what it gets back or how this differs from get_x1_guide.

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 baseline is 3. The description largely restates the workflow enum descriptions already present in the schema rather than adding new syntax, defaults, or interaction rules between topic/states/clientId and workflow.

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

Purpose3/5

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

'Get role-aware guidance' states a verb and resource, but the sentence immediately dissolves into an enumeration of workflow values, so it is unclear whether the tool returns guidance text, routes to a workflow, or produces artifacts. No differentiation from the very similar sibling get_x1_guide, leaving the agent unable to tell the two guides apart.

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

Usage Guidelines4/5

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

Provides explicit routing with exclusions: 'use money_check for dated official state unclaimed-property destinations, not search results' and 'use review_capital_call only for a capital-call notice'. This is when-to-use guidance for the workflow values, though it never says when to prefer this tool over get_x1_guide.

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

All X1 Wealth toolsInspect
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.

Resources