Skip to main content
Two tools let an assistant know who it is talking to and what it is allowed to do before it acts. get_user_info reads your profile, plan, feature flags and quotas; set_user_preferences updates the profile fields that shape tax guidance. Full parameters are on the tools reference.
Responses reflect your live AI2Fin account. A plan-gated call never throws — it returns tool_failed with requiredPlans and an upgradeUrl, so the assistant can explain rather than fail silently.

get_user_info

set_user_preferences

Any subset of countryCode (ISO code), businessType (INDIVIDUAL, SOLE_TRADER, COMPANY, …), industry, profession, aiContextInput (a note the assistant should keep in mind) and hasStudyLoan (true to include compulsory study-loan repayments in the tax forecast, null to clear). Returns { userId, updated: [...] } naming the fields that changed. It is a write, so clients other than Meta Muse (which asks the user itself) confirm it with a confirmToken first; Muse is not offered this tool at all.

Which plan unlocks which tools

Plan gates come from the tool registry (the Plan column of the published catalogue at https://api.ai2fin.com/.well-known/mcp-server/tools.json). Feature flags are checked per call; some tools gate only certain views or actions.
Premium features include a small free allowance so you can try them before upgrading. Once it is used, the tool returns the upgrade message above; free features stay available on every plan.

Typical flow

  1. The assistant calls get_user_info with view: "feature_access" and feature: "ai_categorization".
  2. It sees hasAccess: false and upgradeRequired: true.
  3. It tells you which plan unlocks the feature and points at upgradeUrl instead of attempting the gated call.

Next steps

Transaction tools

Query, analyse and edit transactions

Bill tools

Recurring bills and payments