Skip to main content
Glama

numerology_profile

Full deterministic Pythagorean numerology profile from a name and birth date: Life Path, Expression/Destiny, Soul Urge, Personality, Birthday, Maturity and Personal Year, each with reduction trail. No AI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYes
nameNo
yearYes
monthYes
targetYearNo

TDQS

A3.9/5.0
Behavior4/5

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

Discloses key behavioral trait: deterministic ('No AI'). Lists all output components with reduction trail. No annotations provided, so description carries burden; it does well but could mention error handling or missing parameter 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?

Single, efficiently worded sentence. Every phrase adds value: 'deterministic', 'full profile', 'each with reduction trail'. Front-loaded and no fluff.

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?

No output schema, but description compensates by listing all output components and mentioning reduction trail. Could clarify optionality of name and purpose of targetYear for full completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%. Description only mentions 'name and birth date' but does not explain all 5 parameters (e.g., targetYear is missing). Adds some meaning but incomplete.

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?

Description clearly states the tool generates a full Pythagorean numerology profile from name and birth date, listing specific components (Life Path, Expression, etc.). It distinguishes from siblings (compatibility, life_path, name_numbers) by being a comprehensive profile.

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?

No explicit guidance on when to use this vs sibling tools. The 'No AI' hint is useful but doesn't compare to alternatives like 'compatibility' or 'life_path'.

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.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool targets a distinct aspect of Pythagorean numerology (life path, name numbers, compatibility, full profile) with no overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent pattern of lowercase, underscore-separated descriptive words (e.g., life_path, numerology_profile).

Tool Count5/5

With 4 tools, the server covers the core numerology functions without being too sparse or bloated, fitting its focused purpose.

Completeness5/5

The tool set covers all major Pythagorean numerology components: Life Path, Expression, Soul Urge, Personality, Birthday, Maturity, Personal Year, and compatibility.

Resources