Skip to main content
Glama

AstroWay Astrology API (full catalogue)

Generate Tarot Reading (PDF or HTML)

astroway_reports_tarot

Render a tarot reading PDF. Default spread three-card (Past/Present/Future from Rider-Waite-Smith deck). Available spreads: single-card, three-card, celtic-cross, horseshoe, relationship, year-ahead, decision, chakra, career, love-triangle. Pass seed for reproducibility (deterministic mulberry32 RNG); omit to use a daily seed. Set allowReversed: false to draw upright cards only.

[Group: Reports] [Endpoint: POST /v1/reports/tarot] [Cost: 100 credits (Tier 4)]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astroway_reports_tarot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
seedNo
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
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.
spreadNo
languageNo
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
whitelabelNo
allowReversedNo

Output Schema

NameRequiredDescriptionDefault
urlNo
expires_atNo
page_countNo
byte_lengthNo
duration_msNo
storage_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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. Changed13 schema fields changed
    • changedInput schema / properties / whitelabel / anyOf
      Previous value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "backgroundColor": {
      -        "pattern": "^#([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$",
      -        "type": "string"
      -      },
      -      "companyBio": {
      -        "maxLength": 500,
      -        "type": "string"
      -      },
      -      "companyEmail": {
      -        "format": "email",
      -        "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      -        "type": "string"
      -      },
      -      "companyMobile": {
      -        "maxLength": 40,
      -        "type": "string"
      -      },
      -      "companyName": {
      -        "maxLength": 80,
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "companyUrl": {
      -        "format": "uri",
      -        "type": "string"
      -      },
      -      "fontPairing": {
      -        "enum": [
      -          "serif-sans",
      -          "sans-serif",
      -          "serif-only",
      -          "sans-only",
      -          "system"
      -        ],
      -        "type": "string"
      -      },
      -      "footerText": {
      -        "maxLength": 200,
      -        "type": "string"
      -      },
      -      "frontImage": {
      -        "format": "uri",
      -        "type": "string"
      -      },
      -      "headingColor": {
      -        "description": "Colour of the divider rule under each section heading (not the heading text, which is themeColor).",
      -        "pattern": "^#([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$",
      -        "type": "string"
      -      },
      -      "logoUrl": {
      -        "format": "uri",
      -        "type": "string"
      -      },
      -      "reportName": {
      -        "maxLength": 80,
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "textPrimaryColor": {
      -        "pattern": "^#([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$",
      -        "type": "string"
      -      },
      -      "textSecondaryColor": {
      -        "pattern": "^#([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$",
      -        "type": "string"
      -      },
      -      "themeColor": {
      -        "description": "Accent colour, used for section heading text and inline emphasis.",
      -        "pattern": "^#([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "backgroundColor": {
      +        "pattern": "^#([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$",
      +        "type": "string"
      +      },
      +      "companyBio": {
      +        "maxLength": 500,
      +        "type": "string"
      +      },
      +      "companyEmail": {
      +        "format": "email",
      +        "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      +        "type": "string"
      +      },
      +      "companyMobile": {
      +        "maxLength": 40,
      +        "type": "string"
      +      },
      +      "companyName": {
      +        "maxLength": 80,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "companyUrl": {
      +        "format": "uri",
      +        "type": "string"
      +      },
      +      "fontPairing": {
      +        "enum": [
      +          "serif-sans",
      +          "sans-serif",
      +          "serif-only",
      +          "sans-only",
      +          "system"
      +        ],
      +        "type": "string"
      +      },
      +      "footerText": {
      +        "maxLength": 200,
      +        "type": "string"
      +      },
      +      "frontImage": {
      +        "format": "uri",
      +        "type": "string"
      +      },
      +      "headingColor": {
      +        "description": "Colour of the divider rule under each section heading (not the heading text, which is themeColor).",
      +        "pattern": "^#([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$",
      +        "type": "string"
      +      },
      +      "logoUrl": {
      +        "format": "uri",
      +        "type": "string"
      +      },
      +      "reportName": {
      +        "maxLength": 80,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "textPrimaryColor": {
      +        "pattern": "^#([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$",
      +        "type": "string"
      +      },
      +      "textSecondaryColor": {
      +        "pattern": "^#([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$",
      +        "type": "string"
      +      },
      +      "themeColor": {
      +        "description": "Accent colour, used for section heading text and inline emphasis.",
      +        "pattern": "^#([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties / byte_length / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / byte_length / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / duration_ms / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / duration_ms / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / expires_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / expires_at / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / page_count / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / page_count / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / storage_key / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / storage_key / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, openWorld=true, destructive=false, so the safety profile is covered. The description adds genuinely new behavior: 100 credits (Tier 4) cost, the POST endpoint, and the crucial determinism model (deterministic mulberry32 with an explicit seed, otherwise a rotating daily seed) which explains why idempotentHint is false. It stops short of saying whether the generated PDF is stored, how long a returned url lives, or auth requirements.

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?

Front-loaded with the action, then the spread list and the seed/allowReversed guidance in three tight sentences. The bracketed [Group]/[Endpoint]/[Cost] footer is template noise, though the cost line does carry decision-relevant information. No redundancy overall.

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, so return values need not be explained, and the cost and determinism are disclosed. However a 9-parameter report generator with only 33% schema coverage leaves the whitelabel branding object, language selection, and `name` wholly undocumented in the description. The mismatch between the "PDF" opening line and the three-format enum could also mislead about what is produced by default.

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?

Schema coverage is only 33%, so the description must carry weight, and it does for the most important gaps: `spread` is an unconstrained string in the schema (maxLength 64) but the description enumerates ten valid spreads, and it explains `seed` and `allowReversed` semantics. It says nothing about `name`, `language`, `precision`, or `whitelabel`, leaving roughly half the parameters undocumented in both places. `format` and `fields` are already covered by schema descriptions.

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?

States a specific verb and resource ("Render a tarot reading PDF") and names the default spread and deck, so an agent knows this produces a formatted reading artifact rather than a raw card draw. It never names a sibling, so the boundary against astroway_ai_interpret_tarot (interpretation) or astroway_tarot_rider_waite_draw_three_card (raw draw) must be inferred. Also, the lead sentence says only "PDF" while the title and format enum allow HTML/markdown.

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?

Provides parameter-level usage guidance: omit seed for the daily seed, pass seed for reproducibility, set allowReversed false for upright-only. It gives no guidance on when to choose this report tool over the draw/interpret siblings, nor any prerequisites about what inputs are expected to be supplied elsewhere. Usage is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources