AstroWay Astrology API (full catalogue)

House number numerology

astroway_numerology_house_number

Read-onlyIdempotent

Total and reduction of a house or flat number, a letter suffix (12B) counted by Chaldean value unless countLetters is false, Cheiro's compound reading and compatibility with the driver and conductor.

[Group: Numerology: Indian] [Endpoint: POST /v1/numerology/house-number] [Required: number] [Cost: 10 credits (Tier 1)]

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": {
      "number": "<number>"
    },
    "name": "astroway_numerology_house_number"
  }
}

Input Schema

Name	Required	Description
`date`	No
`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.
`number`	Yes
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`countLetters`	No	Count a letter suffix (12B) by Chaldean value. Default true.

Output Schema

Name	Required	Description	Default
`input`	No
`notes`	No
`total`	No
`digits`	No
`number`	No
`planet`	No
`letters`	No
`compound`	No
`conventions`	No
`countLetters`	No
`compatibility`	No
`compoundBasis`	No
`compoundReading`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the description's job is lighter. It adds genuinely useful operational context the annotations don't carry: the POST endpoint, the 10-credit Tier 1 cost, and the required 'number' input. Output format is left to the output schema, which is appropriate.

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

Conciseness5/5

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

A single dense sentence front-loads the primary computation, then layers the optional letter-counting rule and the derived readings, followed by compact bracketed metadata. No filler sentences.

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 annotations, a full output schema, and the required-parameter callout, an agent has nearly everything needed to invoke it. The only remaining hole is the undocumented 'date' parameter, which neither the schema description nor the text explains.

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 60%, and the description adds real meaning for the most important input by showing the accepted form ('a letter suffix (12B) counted by Chaldean value unless countLetters is false'), tying the letter-handling behavior to the countLetters flag. It says nothing about the 'date', 'fields', or 'precision' compact-mode parameters, so the gap is not fully closed.

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 computation ('total and reduction of a house or flat number') plus the extra readings produced (Cheiro compound, driver/conductor compatibility), which clearly distinguishes it from sibling numerology tools like mobile_number or vehicle_number. Slightly run-on phrasing but the resource and operation are unambiguous.

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?

Usage is implied by the resource ('house or flat number'), but the description never says when to choose this over astroway_numerology_mobile_number, astroway_numerology_vehicle_number, or the Chaldean chart tools, nor any prerequisites.

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

All AstroWay Astrology API (full catalogue) 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?