AstroWay Reports

Generate Numerology Report (PDF or HTML)

astroway_reports_numerology

A numerology reading as an A4 PDF (default), HTML or Markdown: Life Path, Expression, Soul Urge, Personality, Birthday and Maturity with what each position measures and the meaning of its number, the Balance number, the four pinnacles and challenges with their ages, and the personal year. Same engine and meanings as /numerology/{system}/*, five systems. The name must be in Latin letters (diacritics are dropped); any other letter is refused with 400 NAME_NOT_LATIN rather than counted as zero. No AI. Texts in Ukrainian or English; any other language gets the English document.

[Group: Reports] [Endpoint: POST /v1/reports/numerology] [Required: name, date] [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": {
      "name": "<name>",
      "date": "<date>"
    },
    "name": "astroway_reports_numerology"
  }
}

Input Schema

Name	Required	Description
`date`	Yes
`name`	Yes	Full name in Latin letters; the letter tables hold A to Z. Diacritics are dropped, any other letter is refused with 400 NAME_NOT_LATIN.
`year`	No	Year of the personal-year chapter. Defaults to the current year (UTC).
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`format`	No	`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.
`system`	No	Letter table and master-number rule, as /numerology/{system}/*. Default pythagorean.
`language`	No
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`whitelabel`	No

Output Schema

Name	Required	Description	Default
`url`	No
`expires_at`	No
`page_count`	No
`byte_length`	No
`duration_ms`	No
`storage_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the annotations, it discloses real behavioral detail: PDF mode persists a file and returns a URL while html/markdown are self-contained and not stored, pricing is identical across formats, non-Latin letters are rejected with a 400 NAME_NOT_LATIN rather than silently counted as zero, and unsupported languages fall back to an English document. These are exactly the non-obvious behaviors an agent needs. It stops short of describing rate limits or pagination, and the unmentioned whitelabel block leaves a behavioral area unexplained.

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?

Dense but front-loaded: the deliverable and its sections come first, then format, then constraints and language behavior. The long enumeration sentence is justified by the report's scope. Minor waste in the chart-flavored phrasing around system/precision that doesn't quite match a report tool, but nothing egregious.

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

Completeness4/5

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

With an output schema present, the description need not explain return values, yet it still clarifies the format-dependent response (URL vs. inline document). Cost, name encoding rules, and language fallback are all covered. The remaining hole is the 15-field `whitelabel` object, which is completely unmentioned despite being the most complex part of the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description meaningfully supplements it: it explains that `format` changes both storage and response shape, that `language` only actually produces Ukrainian or English with everything else falling back to English (critical, since the enum lists 21 values), and that `name` is restricted to Latin letters with a specific error otherwise. `system` is described only by cross-reference. The nested `whitelabel` object, `fields` and `precision` get no mention at all.

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 numerology reading as A4 PDF by default, or HTML/Markdown) and enumerates exactly which positions are covered (Life Path, Expression, Soul Urge, Personality, Birthday, Maturity, Balance, pinnacles/challenges, personal year). That is far more specific than a tautology. It does not, however, explicitly separate itself from the large family of per-position numerology siblings (e.g. astroway_numerology_pythagorean_life_path) or from astroway_reports_generate, so an agent must infer the routing.

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?

It offers a cost warning with an explicit instruction to confirm with the user before invoking, which is genuine usage guidance. It also notes equivalence with /numerology/{system}/*, implying this is the full-document route — but the complementary rule (use the individual numerology endpoints when only one number is needed) is never stated. No guidance on choosing the sibling report tools.

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

All AstroWay Reports tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?