Asterwise

Lucky Numbers

asterwise_get_lucky_numbers

Read-onlyIdempotent

Fetches condensed lucky-number guidance for a name and birth date including primary and secondary picks, power number, interpretation, and a date_specific flag.

WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_numerology_profile — if deeper context is required.

INPUT CONTRACT: name and date forwarded upstream without local checks.

DO NOT CONFUSE WITH: asterwise_get_numerology_profile — full multi-section profile, not lucky-number-only payload. asterwise_get_number_meaning — dictionary entry for one integer, not personalised lucky sets.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-lucky-numbers/

Input Schema

Name	Required	Description	Default
`date`	Yes	Date in YYYY-MM-DD format.
`name`	Yes	Person's full name as commonly written; its letters are converted to numerology values.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / name / description

Previous value: -"Person's full name as commonly written; letters are converted to numerology values."New value: +"Person's full name as commonly written; its letters are converted to numerology values."

Changed1 schema field changedSep 7, 2026

changedInput schema / properties / date / description

Previous value: -"Date in YYYY-MM-DD format. Defaults to today when omitted."New value: +"Date in YYYY-MM-DD format."

Changed3 schema fields changedSep 5, 2026

addedInput schema / properties / date / description

Added value: +"Date in YYYY-MM-DD format. Defaults to today when omitted."

addedInput schema / properties / name / description

Added value: +"Person's full name as commonly written; letters are converted to numerology values."

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

Changed2 schema fields changedSep 4, 2026

addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```

changedInput schema / required

Previous value: -[
-  "name",
-  "date",
-  "response_format"
-]New value: +[
+  "name",
+  "date"
+]

First observedApr 22, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description adds the useful disclosure that name and date are forwarded upstream without local checks (no client-side validation). It does not describe rate limits or error behavior, deferring those to an external doc link.

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?

Front-loaded first sentence carries the entire payload summary, followed by clearly labelled WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE sections. Every line maps to a decision the agent must make; nothing is redundant padding.

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

Completeness5/5

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

Coverage is complete for a read-only, closed-world tool with an output schema: purpose, output fields, workflow ordering, sibling disambiguation, and an input-handling caveat are all present. Remaining detail (error contract) is deliberately delegated to a documentation URL.

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 description coverage is 100%, so the baseline would be 3, but the INPUT CONTRACT line adds meaning beyond the schema by stating the parameters are passed through without local validation. It stops short of adding format or edge-case guidance for name/date beyond what the schema already says.

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

Purpose5/5

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

States a specific verb and resource ('Fetches condensed lucky-number guidance') and enumerates the payload (primary/secondary picks, power number, interpretation, date_specific flag). It explicitly separates itself from asterwise_get_numerology_profile and asterwise_get_number_meaning, so an agent can identify it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit workflow block says BEFORE: None — standalone, and AFTER: numerology_profile if deeper context is required. The DO NOT CONFUSE WITH section names two siblings and states the distinguishing condition for each, leaving no routing ambiguity.

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

All Asterwise tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?