Skip to main content
Glama
Sign In
astroway-mcp

astroway-mcp

Official
by astroway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Expression / Destiny (pythagorean)

astroway_numerology_pythagorean_expression
Read-onlyIdempotent

Calculate the Pythagorean Expression (Destiny) number from the letters of a full birth name. Provide name and birth date to get the reduced all-letter numerology value.

Instructions

Calculate the Expression (Destiny) number from full birth name letters (all letters, reduced). Numerology: Pythagorean system.

[Group: Numerology: Pythagorean] [Endpoint: POST /v1/numerology/pythagorean/expression] [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_pythagorean_expression"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
nameYes

Output Schema

NameRequiredDescriptionDefault
dateNo
nameNo
systemNo
expressionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description adds useful context beyond them: the endpoint, required inputs, and a 10-credit cost. It does not describe return values, but an output schema exists, lowering the burden.

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 compact and front-loaded: the calculation appears first, followed by structured metadata for group, endpoint, required parameters, and cost. Every line carries useful information with no filler.

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?

For a simple two-parameter calculation with an output schema and rich annotations, the definition covers cost, required inputs, and methodology. The unexplained role of the required 'date' parameter is the main remaining gap, but the tool is otherwise invocable as defined.

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 0%, so the description must compensate. It clarifies that 'name' should be the full birth name (all letters) but merely lists 'date' as required without explaining its role in an Expression calculation, leaving a meaningful gap.

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: calculating the Expression (Destiny) number using Pythagorean numerology. The parenthetical '(all letters, reduced)' subtly distinguishes it from sibling tools like soul_urge (vowels) and personality (consonants), though it does not explicitly name those alternatives.

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 implied by the clear name and the 'all letters' note, but there is no explicit guidance on when to choose this over the many other Pythagorean numerology siblings (life_path, soul_urge, personality, etc.). No exclusions or prerequisites are stated.

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