Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Soul Urge / Heart's Desire (vedic)

astroway_numerology_vedic_soul_urge
Read-onlyIdempotent

Calculate a Vedic Soul Urge number from the vowels in a full birth name and birth date to reveal core desires and inner motivation.

Instructions

Calculate the Soul Urge number from the vowels of the full birth name. Numerology: Vedic system.

[Group: Numerology: Vedic] [Endpoint: POST /v1/numerology/vedic/soul-urge] [Required: name, date] [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": {
      "name": "<name>",
      "date": "<date>"
    },
    "name": "astroway_numerology_vedic_soul_urge"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
nameYes

Output Schema

NameRequiredDescriptionDefault
dateNo
nameNo
systemNo
soulUrgeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile needs no restatement. The description does add genuinely new behavioral context: the credit cost (10 credits, Tier 1) and the endpoint, which an agent must weigh before calling a paid tool. It says nothing about rate limits or failure modes, so it adds some but not rich context.

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?

One sentence of substance up front followed by compact bracketed metadata lines; every element carries signal (group, endpoint, required params, cost). Slightly tag-heavy relative to the prose, but nothing is redundant.

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, return values need not be described. The definition covers inputs, cost, system variant and endpoint, which is nearly everything needed for a simple two-parameter calculation. Missing only explicit sibling routing and date semantics.

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 description coverage is 0%, so the description must compensate. It does clarify that 'name' must be the full birth name (not a nickname) and that both name and date are required, which is meaningful. However, it never explains what 'date' represents (birth date) or how it is consumed in a Soul Urge calculation, leaving a gap on one of two parameters.

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 verb and resource ('Calculate the Soul Urge number') plus the derivation rule ('from the vowels of the full birth name') and the system ('Vedic'), which is exactly what separates it from the many sibling soul_urge tools (Pythagorean, Kabbalistic, Chaldean). It stops short of naming those siblings explicitly, so it's clear but not fully differentiated in-line.

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?

The system qualifier ('Vedic') implicitly tells the agent when to pick this over Pythagorean or Kabbalistic variants, but there is no explicit when-to-use/when-not statement or named alternative. Usage is inferable only from the group tag and name.

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

Deploy Server

Other Tools