Skip to main content
Glama

The Meaning of Numbers

calculate_core_numbers

Read-onlyIdempotent

Free Pythagorean core numbers from a name and birth date (Life Path, Destiny, Soul Urge, Personality, Birthday). Returns the number and the short static teaser only. Does not write a paid AI reading.

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": {
      "month": "<month>",
      "day": "<day>",
      "year": "<year>"
    },
    "name": "calculate_core_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes
nameNoFull name for Destiny, Soul Urge, Personality
yearYes
monthYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered. The description adds genuinely useful scope information beyond that — the response is a number plus a 'short static teaser only' and no paid AI reading is produced or billed, which prevents an agent from over-promising output. It does not address whether omitting the name field degrades results, but for a pure computation that gap is modest.

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?

Two sentences, zero filler, and the substance (what is computed, what is returned, what is not done) is front-loaded. Every clause carries distinct 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?

An output schema exists, so return values need not be explained, yet the description still characterizes the response as a number plus a static teaser. Combined with read-only annotations, an agent has enough to call this correctly. The remaining gap is behavior when the optional name is absent, which matters for a tool whose output set is derived from that field.

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 only 25% — only 'name' is documented, while month, day and year have no descriptions. The description compensates by stating the inputs are 'a name and birth date' and by mapping name to Destiny, Soul Urge and Personality, which implies name is the optional component feeding three of five numbers. It never states what happens when name is omitted or that only month/day/year are required, leaving a real gap at low coverage.

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?

The description names the resource precisely — Pythagorean core numbers — and enumerates the five outputs (Life Path, Destiny, Soul Urge, Personality, Birthday) derived from a name and birth date. It also carves out a boundary against a paid AI-reading capability, so an agent can distinguish this free computation from a fuller reading. The verb is only implied by the tool name ('Free ... core numbers' rather than 'Calculates ...'), which keeps it just short of a 5.

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

Usage Guidelines4/5

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

Clear context is given: this returns the number plus a static teaser, not a paid AI reading, which tells the agent when the lightweight result is appropriate versus when a fuller reading is needed. It stops short of an explicit 'use X instead' routing statement or prerequisites, so it is strong context without full alternative-selection guidance.

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