neto.es - Personal financial planning for Spain

Showing 25 of 100 from the live probe.

• Get live neto.es MCP server information

  Return the identity and exact version of the live neto.es MCP server handling this call. Use this when the user asks which MCP server version is connected or wants to verify that a deployment or connector refresh reached ChatGPT. This reads live server metadata and does not access or change the user's plan.

• Get connected neto.es account name

  Return the exact account name shown for the neto.es user authenticated through this MCP connection. Use this when the user asks which neto.es account is connected or when checking whether browser and MCP information may belong to different accounts. This does not read or change the financial plan.

• List Available Charts

  List the standard charts available to everyone followed by this user's custom charts. Use the IDs and short descriptions to choose a chart without loading its full metric configuration.

• Get Chart Definition

  Load the full immutable definition for one standard or user-owned custom chart. Use this only when you need implementation detail or a proven example before creating a custom chart.

• Create Custom Chart

  Create exactly one immutable custom chart for this user when no standard chart is suitable. Do not include scenario IDs; those are supplied when the chart is rendered.

• List Scenarios

  List all scenarios with their identifiers, names, planning notes, labels, and accent colors.

• List Social Security Contribution Groups

  List Social Security contribution groups (1-11) with human-friendly labels and practical role guidance. Use this when the user needs help choosing a Social Security contribution group while setting up an existing or new employment income. The contribution group should typically come from the user's payroll (nomina). This tool is read-only, it does not change user configuration.

• List Tax Residence Jurisdictions

  List supported Spanish tax residence jurisdictions for IRPF. Use this before setting Comunidad autónoma tax residence when the user's wording needs mapping to an internal id. Includes common-regime autonomous communities, Ceuta/Melilla, Navarra, and the three Basque foral territories.

• Get Yearly Projection Metric Catalog

  List valid yearly `py` projection metrics used for normal LLM analysis, scenario comparisons, milestone logic, and yearly metrics tables. For AI-host responses, because of token size limits, prefer this yearly catalog over the monthly one unless you specifically need chart-level month-by-month detail. Returns metric_id, label, description, measure_type, and value_timing. These metric ids are implicitly from table `py`.

• Get Monthly Projection Metric Catalog

  List valid monthly projection metrics used mainly for chart setup and bounded visual inspection. These metrics are for chart-oriented monthly tables such as `month_summary` and `month_assets`, not yearly `py` analysis. Although monthly metrics are available to the AI host, prefer yearly tools for normal analysis and narration because monthly output is larger (token limits). Returns table and metric_id plus label, description, measure_type, and value_timing. Use table as metric_table_id when a to

• Get Computed Yearly Values For Metrics

  Return computed yearly `py` projection values for the exact scenarios and metrics you request. metric_ids are bare yearly ids implicitly from table `py`. This is the default tool for grounded LLM analysis because yearly output is smaller than monthly output. Use it for comparisons, year-by-year narration, milestone-style reasoning, one-off analytical answers such as 'what is net worth at 65?' or 'when do I reach X?', and yearly metrics-table reasoning. Prefer the monthly tool only when you speci

• Get Computed Monthly Values For Metrics

  Return computed monthly projection values from one selected monthly published table for the exact scenarios and metrics you request. Use metric_table_id to select the monthly table for all requested bare metric_ids. Use this for bounded month-level inspection when timing or row-level detail matters. month_summary is for household totals and decomposable totals. month_assets is for per-asset rows over time. Prefer the yearly tool for normal analysis and narration because monthly output is larger

• Get Scenario Findings

  Return all current advisory findings for valid saved scenario setups without running a projection. Use it after completing or materially changing scenario setup. Findings cover modeling assumptions, open-ended streams, missing financial inputs, and other non-blocking conditions that may deserve review. attention=suggested means relevant review context; none means supporting context. needs_review says whether this occurrence is new for the user. Copy a fresh assessment_item_id into add_workspace_

• Get Projection Assessment

  Evaluate plan objectives and current projection findings for one or two scenarios through one cache-first projection read. Use it before projection conclusions and after projection-driving inputs change. attention=required must be addressed; suggested is relevant context or part of a complete review; none is supporting context. needs_review says whether this scenario-specific occurrence is new for the user. Use plan_status, not attention, to decide whether a plan works. Copy a fresh assessment_i

• Get Public Pension Status

  Read the model's published Spanish public pension status results for one or more scenarios and family members. Use this to understand whether someone qualifies for the ordinary public pension, when retirement starts, why they do or do not qualify, whether recent or total contribution requirements are met, whether historical contribution data is missing, and what initial pension amount the model calculates at retirement. Values are nominal by default. Request value_basis="real_today" for today's

• Get Metric Definition

  Use this for a general meaning or formula question about one metric. Pass metrics as metric_table_id plus bare metric_id. It returns the metric definition, formula structure, and direct dependencies, but not scenario-specific or month-specific values. If the user asks about a concrete projected number, use one of the resolved metric lineage tools instead.

• Create Scenario

  Create a planning scenario with this name. Only call this after the user has confirmed creating the scenario. Use planning_note when the user has stated a concise intention or rationale for the scenario. Omit source_scenario_id to start from default assumption timelines and no planned changes. Provide source_scenario_id when the user wants the new scenario to start as an independent copy of an existing scenario; copied scenario-local events, transactions, and future-created entities receive fres

• Edit Scenario

  Update one existing scenario's name or planning note. Use planning_note for the user's concise scenario intention or rationale; pass an empty string to remove it. A note does not change projections. This tool does not change assumptions, events, future streams, or planned transactions.

• Delete Scenario

  Delete one scenario by scenario_id (assumptions, stream events, and planned transactions). Current-state data is unchanged. You cannot delete the last remaining scenario. If the user wants a clean start without deleting the scenario, use clearScenario instead.

• Clear Scenario

  Clear one scenario while keeping the scenario itself. This removes only that scenario's future plan: planned changes, future stream events, household tax changes, real-estate operating changes, planned transactions, and explicit assumption changes. Growth and other assumption timelines are set back to default values. This does not change or remove current situation data such as family members, tax residence, current assets, liabilities, income, expenses, real estate, Social Security history, bas

• Reorder Scenarios

  Set the complete display order of saved scenarios. Provide every current scenario id exactly once. The app derives A, B, C, and later labels from this order; scenario ids, names, colors, and planning data do not change.

• Get Current State Snapshot

  Return the current factual household setup only: Household Details (family members plus tax residence), current assets, liabilities, incomes, and expenses that exist now, plus global base_decisions. Today base_decisions contains household-wide settings such as cashflow_destination_asset_id, which is the asset where surplus cashflow is directed. This planning system already assumes the household lives in Spain. In current_state, tax_residence_jurisdiction_id means the household's Comunidad autono

• Get Current Snapshot Month

  Read the latest month represented by the shared Starting point and the derived projection start month. Use this before reasoning about the boundary between current facts and scenario futures. The projection always starts in the following month and cannot be set independently.

• Preview Current Snapshot Month Change

  Preview, without saving, exactly how moving current_snapshot_month forward would clip planned changes across every scenario. Always use this before setCurrentSnapshotMonth. Return the effects and blockers to the user, and preserve the returned user_config_etag and preview_token for an exact commit.

• Set Tax Residence Jurisdiction

  Set the household's Comunidad autónoma tax residence in current_state.tax_residence_jurisdiction_id. This updates the visible Household Details section, not Current snapshot. Use this before tax-sensitive projection reads or tax-sensitive answers when getCurrentStateSnapshot shows it is missing. If the user gives a natural place name and you are not certain of the exact id, call listTaxResidenceJurisdictions first.