Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Generate Business Astrology Report (PDF or HTML)

astroway_reports_business

Generates a business founding-chart report from birth data, interpreting Sun, MC, Jupiter and Saturn for purpose, reputation, growth and structure. Outputs PDF, HTML or Markdown; not financial advice.

Instructions

Founding-chart analysis (mundane astrology). Highlights Sun (purpose), MC (reputation), Jupiter (growth), Saturn (structure). Disclaimer: "not financial advice".

[Group: Reports] [Endpoint: POST /v1/reports/business] [Required: chart] [Cost: 5,000 credits (Tier 7)] ⚠️ Premium — ~50% of free monthly budget. Confirm with user before invoking.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chart": "<chart>"
    },
    "name": "astroway_reports_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
chartYesBirth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as "Placidus" is refused, and the case matters because I and i are two different Sunshine systems.
formatNo`pdf` (default) stores a PDF and answers with its `url`. `html` returns one self-contained `text/html` document, `markdown` returns `text/markdown` with the same sections and tables; neither is stored. Same price in every format.
languageNo
whitelabelNo

Output Schema

NameRequiredDescriptionDefault
urlNo
expires_atNo
page_countNo
byte_lengthNo
duration_msNo
storage_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.6.1
    • changedInput schema / properties / chart / allOf
      Previous value: -[
      -  {
      -    "additionalProperties": {
      -      "anyOf": [
      -        {},
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "description": "Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems.",
      -    "properties": {
      -      "ayanamsa": {
      -        "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
      -        "enum": [
      -          "fagan-bradley",
      -          "lahiri",
      -          "de-luce",
      -          "raman",
      -          "krishnamurti",
      -          "kp",
      -          "yukteshwar",
      -          "jn-bhasin",
      -          "true-citra",
      -          "djwhal-khul"
      -        ],
      -        "type": "string"
      -      },
      -      "ayanamsaId": {
      -        "type": [
      -          "number",
      -          "null"
      -        ]
      -      },
      -      "city": {
      -        "default": "",
      -        "type": "string"
      -      },
      -      "cosmogram": {
      -        "type": "boolean"
      -      },
      -      "date": {
      -        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      -        "type": "string"
      -      },
      -      "houseSystem": {
      -        "default": "P",
      -        "enum": [
      -          "P",
      -          "K",
      -          "R",
      -          "C",
      -          "E",
      -          "W",
      -          "B",
      -          "M",
      -          "O",
      -          "A",
      -          "T",
      -          "V",
      -          "D",
      -          "F",
      -          "G",
      -          "H",
      -          "I",
      -          "i",
      -          "L",
      -          "N",
      -          "Q",
      -          "S",
      -          "U",
      -          "X",
      -          "Y"
      -        ],
      -        "type": "string"
      -      },
      -      "latitude": {
      -        "maximum": 90,
      -        "minimum": -90,
      -        "type": "number"
      -      },
      -      "longitude": {
      -        "maximum": 180,
      -        "minimum": -180,
      -        "type": "number"
      -      },
      -      "name": {
      -        "default": "",
      -        "type": "string"
      -      },
      -      "time": {
      -        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      -        "type": "string"
      -      },
      -      "timezone": {
      -        "description": "IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.",
      -        "type": "string"
      -      },
      -      "timezoneOffset": {
      -        "anyOf": [
      -          {
      -            "maximum": 14,
      -            "minimum": -14,
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": 0,
      -        "description": "Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent."
      -      },
      -      "zodiacType": {
      -        "enum": [
      -          "tropical",
      -          "sidereal"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "date",
      -      "time",
      -      "latitude",
      -      "longitude"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": {
      -      "anyOf": [
      -        {},
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "properties": {
      -      "latitude": {
      -        "description": "Birth latitude. Required here: the whole document is computed from it.",
      -        "maximum": 90,
      -        "minimum": -90,
      -        "type": "number"
      -      },
      -      "longitude": {
      -        "description": "Birth longitude. Required here: the whole document is computed from it.",
      -        "maximum": 180,
      -        "minimum": -180,
      -        "type": "number"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {
      +      "anyOf": [
      +        {},
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "description": "Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems.",
      +    "properties": {
      +      "ayanamsa": {
      +        "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
      +        "enum": [
      +          "fagan-bradley",
      +          "lahiri",
      +          "de-luce",
      +          "raman",
      +          "krishnamurti",
      +          "kp",
      +          "yukteshwar",
      +          "jn-bhasin",
      +          "true-citra",
      +          "djwhal-khul"
      +        ],
      +        "type": "string"
      +      },
      +      "ayanamsaId": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "city": {
      +        "default": "",
      +        "type": "string"
      +      },
      +      "cosmogram": {
      +        "type": "boolean"
      +      },
      +      "date": {
      +        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +        "type": "string"
      +      },
      +      "houseSystem": {
      +        "default": "P",
      +        "enum": [
      +          "P",
      +          "K",
      +          "R",
      +          "C",
      +          "E",
      +          "W",
      +          "B",
      +          "M",
      +          "O",
      +          "A",
      +          "T",
      +          "V",
      +          "D",
      +          "F",
      +          "G",
      +          "H",
      +          "I",
      +          "i",
      +          "L",
      +          "N",
      +          "Q",
      +          "S",
      +          "U",
      +          "X",
      +          "Y"
      +        ],
      +        "type": "string"
      +      },
      +      "latitude": {
      +        "maximum": 90,
      +        "minimum": -90,
      +        "type": "number"
      +      },
      +      "longitude": {
      +        "maximum": 180,
      +        "minimum": -180,
      +        "type": "number"
      +      },
      +      "name": {
      +        "default": "",
      +        "type": "string"
      +      },
      +      "time": {
      +        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      +        "type": "string"
      +      },
      +      "timezone": {
      +        "description": "IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.",
      +        "type": "string"
      +      },
      +      "timezoneOffset": {
      +        "anyOf": [
      +          {
      +            "maximum": 14,
      +            "minimum": -14,
      +            "type": "number"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": 0,
      +        "description": "Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent."
      +      },
      +      "zodiacType": {
      +        "enum": [
      +          "tropical",
      +          "sidereal"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "date",
      +      "time",
      +      "latitude",
      +      "longitude"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": {
      +      "anyOf": [
      +        {},
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "properties": {
      +      "latitude": {
      +        "description": "Birth latitude. Required here: the whole document is computed from it.",
      +        "maximum": 90,
      +        "minimum": -90,
      +        "type": "number"
      +      },
      +      "longitude": {
      +        "description": "Birth longitude. Required here: the whole document is computed from it.",
      +        "maximum": 180,
      +        "minimum": -180,
      +        "type": "number"
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
    • changedInput schema / properties / chart / description
      Previous value: -"Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems."New value: +"Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems."
    • addedInput schema / properties / format
      Added value: +{
      +  "description": "`pdf` (default) stores a PDF and answers with its `url`. `html` returns one self-contained `text/html` document, `markdown` returns `text/markdown` with the same sections and tables; neither is stored. Same price in every format.",
      +  "enum": [
      +    "pdf",
      +    "html",
      +    "markdown"
      +  ],
      +  "type": "string"
      +}
  2. Addedv1.6.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the operation is not read-only and is open-world, but the description adds real value with the credit cost, the premium-budget warning and the explicit confirm-first instruction, plus the 'not financial advice' disclaimer. It does not say what gets persisted or how the report is delivered, though the format parameter's schema text covers the pdf-stored vs html/markdown-transient distinction.

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

Conciseness4/5

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

The content is short and front-loaded: what is analysed, which factors, the disclaimer, then bracketed metadata for group, endpoint, required param and cost. The bracketed block is slightly operational rather than descriptive, but every line carries information an agent needs.

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

Completeness3/5

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

An output schema exists and the schema covers birth-data mechanics thoroughly, so the description need not explain returns. What is missing for a high-cost report tool is the report's structure/scope and any hint about scale (how long the PDF is) or what happens on repeat calls, given idempotentHint=false and a per-call credit charge.

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?

Only the required parameter is called out ('Required: chart'), and the description adds no meaning for format, language or whitelabel beyond what the schema already says. Schema coverage is around 50%, but the covered fields carry long explanatory text and the title itself signals the PDF/HTML output choice, so the description is adequate rather than compensating.

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

Purpose4/5

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

The description names a concrete deliverable — a founding-chart analysis in mundane astrology, with the specific factors interpreted (Sun/purpose, MC/reputation, Jupiter/growth, Saturn/structure). That is a clear verb-adjacent statement of what gets produced. It does not, however, distinguish itself from the very similarly-named sibling astroway_business_founding_chart, leaving the agent unsure which of the two to reach for.

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 definition says to confirm with the user before invoking because of the 5,000-credit premium (~50% of a free monthly budget), which is genuinely useful invocation guidance. It offers no guidance on when this report is the right choice versus the other business_* tools or astroway_reports_generate, so the use case has to be inferred from the subject matter.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools