Skip to main content
Glama

X1 Wealth

by com.x1wealth
OverviewDiscussionsAdmin

X1 Workflow Guide

get_x1_workflow_guide
Read-onlyIdempotent

Get role-aware guidance for financial_workbench analysis, document comparisons, scenarios, and briefs, 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

TableJSON 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.
clientIdNoAuthorized client/member ID when already known. If unknown, start from roster/search tools first.
workflowNoWorkflow 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.

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; 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"
+]
  2. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds only that it returns 'full production app URLs' and is 'role-aware', but does not disclose what the guidance contains, length, or limitations. With annotations covering safety, the bar is lower, but this still adds little beyond the schema.

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

Conciseness1/5

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

The description is a single sprawling sentence that crams two purposes and a long list of workflow artifacts without structure or front-loading. It is difficult to parse and violates conciseness principles.

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

Completeness2/5

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

Given 4 parameters, two enums, read-only annotations, and no output schema, the description should clarify the relationship between workflow selection and guidance topics, and what the output entails. It omits output format entirely and conflates two distinct functions, leaving the agent unsure of expected results.

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 each parameter already has a description. The description adds 'role-aware' context and mentions full production app URLs, but does not explain parameter interactions or defaults beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose2/5

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

The description lists topics and workflow artifacts but the core purpose is buried in a dense run-on sentence. It reads as a catalog rather than a clear statement of what the tool does, and it is hard to distinguish from siblings like get_x1_guide or get_what_matters_now.

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 enum parameter description provides conditional guidance (e.g., 'Use financial_workbench for broad financial questions', 'Use review_capital_call only for a capital-call notice'), which implies when to use certain workflows. However, the top-level description offers no explicit when-to-use guidance or alternatives to this guide tool itself.

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
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