AstroWay Numerology

Vehicle number numerology

astroway_numerology_vehicle_number

Read-onlyIdempotent

Same shape as the mobile number for a number plate: every digit counts, the letters (the state and district code on an Indian plate) only with countLetters, by Chaldean value.

[Group: Numerology: Indian] [Endpoint: POST /v1/numerology/vehicle-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_vehicle_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 the letters by Chaldean value too. Default false: the letters of an Indian plate are the state and district code.

Output Schema

Name	Required	Description	Default
`input`	No
`notes`	No
`pairs`	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.6/5.0

Behavior4/5

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

Annotations already establish a safe, idempotent, closed-world read, so the description's added value is the Chaldean counting rule, the treatment of letters, the credit cost, and the POST endpoint. It does not spell out return content, but an output schema exists, so that omission is acceptable.

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?

A single dense sentence plus compact metadata blocks; almost nothing is wasted. The lead phrase 'Same shape as the mobile number' is slightly indirect as an opener, but it is immediately given meaning by 'for a number plate'.

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?

Output schema and annotations cover much of the surface, and the description covers the domain-specific counting logic. It does not explain the role of the optional `date` field or whether it affects the result, which is a genuine gap for a 5-parameter tool.

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?

The description adds real meaning beyond the schema for two parameters: 'every digit counts' for `number` and the state/district-code reasoning behind `countLetters`. With schema coverage at 60%, `date`, `fields`, and `precision` are left to the schema, so the description only partially compensates for the gap.

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 states a specific resource (a vehicle number plate) and method (Chaldean value), and clearly ties this tool to the sibling mobile-number tool as its reference shape. It does not literally name the verb 'computes numerology', but 'same shape as the mobile number for a number plate' makes the operation unambiguous to an agent already familiar with the family.

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 through the comparison with the mobile-number tool and the domain hint (Indian plates), but there is no explicit statement of when to prefer this over astroway_numerology_mobile_number or astroway_numerology_house_number. The cost tier and endpoint metadata help an agent decide to call it, but not between siblings.

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

All AstroWay Numerology 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?