Doğum Haritası (Türkçe)

Doğum haritası hesapla

natal_chart

Doğum tarihi, saati ve yerinden gezegen konumları, evler ve açıları üretir (Türkçe).

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>",
      "birthdate": "<birthdate>",
      "birthtime": "<birthtime>",
      "birthplace": "<birthplace>",
      "country": "<country>"
    },
    "name": "natal_chart"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Kişinin adı
`country`	Yes	ISO 3166-1 alpha-2 ülke kodu
`birthdate`	Yes	YYYY-MM-DD
`birthtime`	Yes	HH:MM (24 saat)
`birthplace`	Yes	Doğum şehri

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, but it does not state the house system, ephemeris or accuracy characteristics, timezone handling, whether the operation is read-only, or what the result contains. It only asserts that positions, houses and aspects are produced.

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?

The definition is a single efficient sentence with the main outputs and inputs front-loaded, and there is no unnecessary wording. It is slightly under-specified rather than padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-parameter computation tool with no annotations and no output schema, so the description should explain more about the computation and result. It omits house-system choice, timezone handling, output format, and behavioral constraints, leaving significant gaps for correct invocation.

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 100%, so the five parameters and their formats are already documented in the schema. The description summarizes the inputs as birth date, time and place but adds no format details, validation rules, or explanation of fields like name or country beyond the schema, making the baseline 3 appropriate.

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 uses a specific verb (üretir) and names the concrete outputs: planetary positions, houses and aspects, derived from birth date, time and place. It is clear what the tool does, though it lacks differentiation from any alternative chart or astrology tools.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no prerequisites such as timezone or house-system assumptions, and no exclusions. The agent must infer usage entirely from the one-sentence purpose.

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

All Doğum Haritası (Türkçe) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?