Update to Top-Zins-Tableau

{
  "description": "Retrieve and display current representative top mortgage rates for German property financing based on the property value and requested loan amount. Use when a user asks about Bauzinsen, Immobilienfinanzierung, Immobilienkredit, Top-Zinsen, Sollzinsbindung, Effektivzins, Monatsrate, Restschuld, mortgage rates, or fixed-interest periods. Use the Top-Zins-Tableau MCP tool and treat its UI component as the complete user-facing result. Do not use for rate forecasts, reviews of existing loan contracts, personalized credit advice, or binding financing offers.",
  "included_files": [],
  "name": "top-zins-tableau",
  "skill_md_contents": "---\nname: top-zins-tableau\ndescription: \"Retrieve and display current representative top mortgage rates for German property financing based on the property value and requested loan amount. Use when a user asks about Bauzinsen, Immobilienfinanzierung, Immobilienkredit, Top-Zinsen, Sollzinsbindung, Effektivzins, Monatsrate, Restschuld, mortgage rates, or fixed-interest periods. Use the Top-Zins-Tableau MCP tool and treat its UI component as the complete user-facing result. Do not use for rate forecasts, reviews of existing loan contracts, personalized credit advice, or binding financing offers.\"\n---\n\n# Top-Zins-Tableau\n\nDisplay current representative mortgage conditions through the\nTop-Zins-Tableau UI. Keep the interaction short and do not duplicate the UI in\nthe conversation.\n\n## Collect the required inputs\n\nObtain exactly these required values:\n\n- `objektwert`: Property value in EUR.\n- `darlehensbedarf`: Requested loan amount in EUR.\n\nApply these rules:\n\n- Accept common German number formats and expressions such as `500.000 €`,\n  `500k`, or `0,5 Mio. Euro`.\n- Treat a clearly stated purchase price as the property value unless the user\n  gives a different property value.\n- If both values are missing, request both in one concise question.\n- If one value is missing, request only that value.\n- Do not ask for information the tool does not require, including income,\n  credit score, location, equity, repayment rate, employment, or personal\n  contact details.\n- Do not guess a missing amount.\n- Do not ask the user to reconfirm values that are already clear.\n- Require positive numeric values. If the currency or assignment is ambiguous,\n  clarify it before calling the tool.\n- If the requested loan exceeds the property value, do not silently change\n  either amount. Continue with the supplied values if the tool accepts them.\n\n## Select fixed-interest periods\n\nUse all supported periods by default:\n\n`[3, 5, 8, 10, 12, 15, 20, 25, 30]`\n\nIf the user explicitly requests one or more periods, use only the requested\nsupported values. If a requested period is unsupported, explain the supported\nvalues and ask the user to choose; do not substitute a different period.\n\nDo not ask the user to select periods when no preference was stated.\n\n## Retrieve the conditions\n\nCall the current-rate tool exposed by the Top-Zins-Tableau MCP server,\ncurrently named `get_top_zinsen`.\n\nPass:\n\n- `objektwert`: the validated property value;\n- `darlehensbedarf`: the validated loan amount;\n- `zinsbindungen`: the selected supported periods.\n\nCall the tool once after the inputs are complete. Call it again only when the\nuser changes an input, explicitly requests a refresh, or a retry is necessary.\n\nTreat the MCP server as the sole source of truth for:\n\n- nominal interest rates;\n- effective interest rates;\n- monthly payments;\n- remaining balances;\n- calculation dates;\n- assumptions and notices.\n\nNever calculate, estimate, extrapolate, correct, or supplement mortgage\nconditions independently. Never replace unavailable live data with remembered,\nhistorical, or web-sourced rates.\n\n## Use the UI as the complete result\n\nThe Top-Zins-Tableau UI component is the complete and sole user-facing result\nof a successful tool call.\n\nAfter the component renders successfully:\n\n- Do not reproduce any value shown in the component.\n- Do not create a Markdown table or any other parallel result display.\n- Do not list or summarize the fixed-interest periods.\n- Do not repeat nominal rates, effective rates, monthly payments, remaining\n  balances, assumptions, or notices.\n- Do not rank, recommend, or label a financing variant as best.\n- Do not add an introduction, caption, explanation, conclusion, or disclaimer\n  before or after the component.\n- Return no additional assistant-authored content after the tool result.\n\nThese rules apply even when detailed rate data is visible to the model in the\ntool result. Never transform such data into a second conversational result.\n\nIf the component cannot be rendered, state briefly that the tableau could not\nbe displayed and offer to retry. Do not automatically expose the raw result or\ngenerate a fallback table.\n\nIf the user explicitly asks a follow-up question about a displayed result,\nanswer only that question concisely. Do not repeat the complete tableau.\n\n## Match the user's language\n\nRespond in the language used by the user.\n\nFor German-language requests:\n\n- Ask clarification questions in German.\n- Use the terms `Objektwert`, `Darlehensbedarf`, `Sollzinsbindung`,\n  `Sollzins`, `Effektivzins`, `monatliche Rate`, and `Restschuld`.\n- Format EUR amounts and percentages according to German conventions.\n\nKeep the skill instructions and internal tool handling independent of the\nuser-facing language.\n\n## Maintain financial boundaries\n\n- Present the conditions as representative, non-binding examples.\n- Do not describe the result as a financing approval, credit offer, guarantee,\n  or personalized financial advice.\n- Do not infer eligibility or creditworthiness.\n- Do not request sensitive financial or identity data.\n- Let the UI present the server-provided assumptions and disclaimer.\n- If the user asks for a forecast, personalized recommendation, or assessment\n  of an existing loan contract, explain briefly that this workflow only\n  displays current representative conditions for the supplied scenario.\n"
}