Skip to main content
Glama

Asterwise

by com.asterwise.mcp
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format.
nameYesPerson's full name as commonly written; letters are converted to numerology values.
response_formatNoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed3 schema fields changed
    • 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."
  3. Changed2 schema fields changed
    • addedInput schema / properties / response_format / default
      Added value: +"markdown"
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "date",
-  "response_format"
-]New value: +[
+  "name",
+  "date"
+]
  4. First observed

TDQS

A4.5/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 behavior. The description adds useful behavioral context beyond annotations: the tool is 'condensed', includes a 'date_specific flag', and forwards name/date 'upstream without local checks'. It also links to the full output and error contract, though it does not detail failure modes inline.

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?

The description is well-structured with a front-loaded summary, then compact WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE sections. Every sentence adds distinguishing or operational value, and the documentation link avoids bloating the description further.

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?

For a simple read-only, idempotent, 3-parameter tool with a full input schema and an output schema present, the description is complete. It covers workflow, input contract, sibling differentiation, and points to the authoritative documentation for output and error details.

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 100%, so the schema already documents name, date, and response_format with formats, defaults, and enums. The description adds no new parameter-level semantics beyond calling date a 'birth date', which the schema already captures. Baseline 3 is appropriate.

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?

The description opens with a specific verb and resource: 'Fetches condensed lucky-number guidance for a name and birth date' and enumerates exact payload elements. It also explicitly differentiates from nearby siblings in the 'DO NOT CONFUSE WITH' section, so an agent can identify the tool unambiguously.

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?

The workflow section states there is no prerequisite, and that asterwise_get_numerology_profile should be used afterward if deeper context is needed. The DO NOT CONFUSE section explicitly names the alternatives and the conditions that make them inappropriate, giving clear when-to-use and when-not-to-use guidance.

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

All Asterwise toolsInspect
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