Skip to main content
Glama

AstroLogics

Numerology numbers

get_numerology
Read-onlyIdempotent

Calculate numerology core numbers from a full name and birth date: life path, birth, destiny (expression), soul urge, personality and personal year numbers, with meanings, lucky numbers, colours and days, and the ruling planet.

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": "get_numerology"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
nameYesFull name as the person uses it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered and the bar is lower. The description adds real value by disclosing the calculation outputs (lucky numbers, colours, days, ruling planet), but it says nothing beyond annotations about computation basis, validity of input dates, or error behavior.

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 front-loaded sentence that names the verb, the resource, and the returned numbers, then lists supplementary outputs. No filler, no redundancy, nothing that could be trimmed without losing information.

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?

The tool is simple (two required inputs, no nesting, no output schema), and the description enumerates what comes back, so an agent knows what to expect. Minor gaps remain: no mention of how the personal-year number depends on the current date, and no error handling guidance.

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% with only two parameters, both fully documented (YYYY-MM-DD pattern, full name). The description does reinforce that both name and birth date feed the calculation, which clarifies their joint role, but adds no format or edge-case guidance beyond the schema. Baseline 3.

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?

Uses a specific verb ("Calculate") with a named resource ("numerology core numbers") and enumerates the outputs returned: life path, birth, destiny/expression, soul urge, personality, personal year. The domain is plainly distinct from the astrology-oriented siblings, though the description never explicitly contrasts itself with them.

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 only implied: the agent can infer it needs a full name and birth date, but there is no statement of when to reach for this versus other tools, no prerequisites, and no exclusions. Adequate minimum-viable guidance, nothing more.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources