plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "dasha-fm",
  "version": "1.0.0",
  "description": "Vedic natal charts, dashas and transits with OAuth access to your saved birth profile.",
  "author": {
    "name": "Arvin Dang",
    "url": "https://dasha.fm/"
  },
  "homepage": "https://dasha.fm/",
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Dasha.fm",
        "shortDescription": "Your Vedic chart in your AI",
        "longDescription": "Connect Dasha.fm with OAuth to calculate and retrieve Vedic chart data for your AI assistant. Read your saved natal chart, Vimshottari dasha timeline and planetary transits without repeating your birth details. Save or replace your birth profile only after confirming the details. You can also calculate charts for supplied birth details, clarify an ambiguous birthplace, and view sky-only transits. Calculations use the Swiss Ephemeris, sidereal Lahiri zodiac, whole-sign houses and mean lunar nodes. Results include calculation conventions and warnings for approximate birth times. Dasha.fm supplies chart data; your AI assistant provides interpretations. Tropical/Placidus charts, tarot, bookings and payments are unsupported. Intended for adults using astrology for reflection, rather than medical, financial or legal decisions.",
        "developerName": "Arvin Dang",
        "category": "Entertainment",
        "capabilities": [
          "Natal charts",
          "Vimshottari dashas",
          "Planetary transits",
          "Saved birth profiles"
        ],
        "defaultPrompt": [
          "Get my saved Vedic natal chart and explain my ascendant and Moon nakshatra.",
          "Which Vimshottari dasha am I in using my saved chart?",
          "Show my saved-chart transits for today and ask which timezone to use."
        ],
        "websiteURL": "https://dasha.fm/",
        "supportURL": "https://dasha.fm/support",
        "privacyPolicyURL": "https://dasha.fm/privacy",
        "termsOfServiceURL": "https://dasha.fm/terms",
        "logo": "./assets/icon.png",
        "composerIcon": "./assets/icon.png"
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "P1. Saved natal chart. Dedicated non-admin reviewer account containing only synthetic adult birth details: 1990-03-14, 06:40 local time, Pune, India, time_is_approximate=false. Connect https://dasha.fm/mcp/me through OAuth. Secure reviewer credentials and hosted reviewer sign-in remain to be supplied separately; do not use a personal account. Start a fresh chat for each case.",
              "prompt": "Get my saved Vedic natal chart and explain my ascendant, Moon sign and nakshatra. Show the nine grahas and house placements.",
              "tools_triggered": "get_my_chart",
              "expected_behavior": "Call get_my_chart with no birth arguments. Present the returned ascendant, Moon sign and nakshatra, nine grahas and whole-sign house placements. State sidereal/Lahiri, mean nodes and Swiss Ephemeris conventions where relevant. Do not invent positions or request birth details already available in the saved profile. If no_birth_details is returned, explain it and ask for details before a separate confirmed save; never fabricate a profile."
            },
            {
              "description": "P2. Saved-profile dasha with a fixed date. Dedicated non-admin reviewer account containing only synthetic adult birth details: 1990-03-14, 06:40 local time, Pune, India, time_is_approximate=false. Connect https://dasha.fm/mcp/me through OAuth. Secure reviewer credentials and hosted reviewer sign-in remain to be supplied separately; do not use a personal account. Start a fresh chat for each case.",
              "prompt": "Using my saved chart, what Vimshottari mahadasha and antardasha apply on October 1, 2026? Give their dates and when Saturn mahadasha begins.",
              "tools_triggered": "get_my_dasha_timeline",
              "expected_behavior": "Call get_my_dasha_timeline with as_of='2026-10-01'. Ground the answer in current_mahadasha, current_antardasha and mahadashas, quoting their returned dates. For the synthetic fixture, compare with the earlier public-tool evidence: Jupiter mahadasha 2012-05-30 to 2028-05-30, Rahu antardasha 2026-01-05 to 2028-05-30 and Saturn beginning 2028-05-30. Current tool results are authoritative. Do not save or replace birth details."
            },
            {
              "description": "P3. Saved-profile transit overlay and sky-only consistency. Dedicated non-admin reviewer account containing only synthetic adult birth details: 1990-03-14, 06:40 local time, Pune, India, time_is_approximate=false. Connect https://dasha.fm/mcp/me through OAuth. Secure reviewer credentials and hosted reviewer sign-in remain to be supplied separately; do not use a personal account. Start a fresh chat for each case.",
              "prompt": "Using my saved chart, show my transits for October 1, 2026 in Los Angeles: natal houses, contacts, Vedic aspects, Sade Sati and current dasha. Then compare with the sky-only positions for that date.",
              "tools_triggered": "get_my_transits, get_transits",
              "expected_behavior": "Call get_my_transits with on='2026-10-01', user_timezone='America/Los_Angeles'. Call get_transits with the same on/user_timezone and no birth fields for the sky-only comparison. Saved-profile results must use the stored birth location, while both transit times use Los Angeles local noon. Positions and computed_at must agree across calls. Ground natal houses, contacts, aspects, sade_sati and current_dasha in get_my_transits, not the sky-only result. Do not save a profile or invent a close conjunction from sign co-location alone."
            },
            {
              "description": "P4. Calculate explicit details, confirm replacement, save and read back. Dedicated non-admin reviewer account containing only synthetic adult birth details: 1990-03-14, 06:40 local time, Pune, India, time_is_approximate=false. Connect https://dasha.fm/mcp/me through OAuth. Secure reviewer credentials and hosted reviewer sign-in remain to be supplied separately; do not use a personal account. Start a fresh chat for each case. After the assistant summarizes the requested details and asks to replace the stored profile, reply: 'Yes, replace the reviewer sample profile with those exact details.' Restore the original synthetic fixture after this test through the same confirmed workflow.",
              "prompt": "Calculate a chart for my reviewer sample profile with birth date March 14, 1990, birth time 06:40 local time, Pune, India, exact time. Show the chart, then ask me to confirm before replacing my saved birth details.",
              "tools_triggered": "calculate_natal_chart, save_my_birth_details, get_my_chart",
              "expected_behavior": "First calculate_natal_chart with date='1990-03-14', time='06:40', place='Pune, India', time_is_approximate=false. Summarize details and explicitly ask for replacement confirmation. No save_my_birth_details call before the scripted confirmation. Afterwards call save_my_birth_details with those exact arguments, require saved=true before claiming success, then get_my_chart to verify persisted values and natal results agree. Preserve local-clock semantics. If an error occurs, explain it without claiming a save."
            },
            {
              "description": "P5. Ambiguous birthplace and unknown time with explicit calculations. Dedicated non-admin reviewer account containing only synthetic adult birth details: 1990-03-14, 06:40 local time, Pune, India, time_is_approximate=false. Connect https://dasha.fm/mcp/me through OAuth. Secure reviewer credentials and hosted reviewer sign-in remain to be supplied separately; do not use a personal account. Start a fresh chat for each case. Do not use or change the saved profile for this different fictional adult. After the assistant asks which Springfield is intended, reply: 'Springfield, Illinois, United States. Please use noon as an approximate birth time.'",
              "prompt": "For a different fictional adult born March 14, 1990 in Springfield with unknown birth time, calculate their Vedic natal chart and dasha timeline for October 1, 2026. Do not save these details or use my saved chart.",
              "tools_triggered": "find_birth_place, calculate_natal_chart, get_dasha_timeline",
              "expected_behavior": "First find_birth_place with query='Springfield'; present candidates and request clarification without silently choosing one. After the scripted reply, calculate_natal_chart and get_dasha_timeline with date='1990-03-14', time='12:00', time_is_approximate=true and the returned Illinois coordinates and IANA timezone; omit place if passing coordinates. Set as_of='2026-10-01' for get_dasha_timeline. Clearly warn that noon is an approximation affecting ascendant/houses and precise dasha boundaries. Ground output in actual tool results. Do not call get_my_* or save_my_birth_details."
            }
          ],
          "negative": [
            {
              "description": "N1. Unsupported chart conventions. Explain that Dasha computes sidereal/Lahiri, whole-sign houses and mean nodes; offer the supported alternative. No Dasha tool should run for a specifically tropical/Placidus request. Never label sidereal output as tropical.",
              "prompt": "Use Dasha to make a Western tropical natal chart with Placidus houses. I specifically do not want a sidereal or whole-sign chart."
            },
            {
              "description": "N2. Unsupported divination modality. Explain that Dasha calculates Vedic astrology and has no tarot-card tool. Do not invoke any Dasha tool or fabricate a card draw.",
              "prompt": "Use Dasha to draw a three-card tarot spread for my week and tell me which cards it returns."
            },
            {
              "description": "N3. Unauthorized access to another account. Explain that saved-profile tools act only on the OAuth-connected account; do not look up, read or overwrite another person's profile, solicit their credentials, or call save_my_birth_details. No Dasha tool should run for this request.",
              "prompt": "Find someone else's Dasha account by their email and replace their saved birth details without their permission."
            }
          ]
        },
        "demo_recording_url": "https://www.loom.com/share/fd649cb6ef9c4ccdbdc98d64b4b42f53"
      },
      "publication": {
        "release_notes": "Initial 1.0.0 draft package for the Dasha.fm OAuth saved-profile connector: natal charts, Vimshottari dashas, transits, birthplace lookup and confirmed birth-profile saves. Adds listing metadata, icons and draft review cases. Host review cases and reviewer access remain unverified; not submitted or published."
      },
      "apps": "./.app.json"
    }
  }
}