Skip to main content
Glama

Gebelik haftası

gebelik_haftasi_hesapla
Read-onlyIdempotent

Son adet tarihinden gebelik haftasını, trimesteri ve tahmini doğum tarihini (Naegele) hesaplar.

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": {
      "sonAdetTarihi": "<sonAdetTarihi>"
    },
    "name": "gebelik_haftasi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
referansTarihNoBoşsa bugün.
sonAdetTarihiYesSon adetin ilk günü.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / referansTarih / description
      Previous value: -"Hangi tarihteki hafta, YYYY-AA-GG. Boşsa bugün."New value: +"Boşsa bugün."
    • changedInput schema / properties / sonAdetTarihi / description
      Previous value: -"Son adet döneminin ilk günü, YYYY-AA-GG."New value: +"Son adetin ilk günü."
  2. 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 destructiveHint=false, covering safety. The description adds the output components (pregnancy week, trimester, due date) and mentions the Naegele rule, which is helpful context beyond annotations, but it does not explain error handling, date format requirements, or how the optional reference date affects results.

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, efficient sentence that front-loads the input source and lists outputs without any redundant wording. Every part of the sentence earns its place.

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?

Given the simple nature of this read-only calculator, full schema descriptions, and annotations, the description is nearly complete. It names the key outputs and the method (Naegele), but it could better clarify how the optional referansTarih parameter influences the calculation (e.g., whether the pregnancy week is computed as of that date).

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 both parameters (sonAdetTarihi and referansTarih) are fully documented in the schema. The description only implicitly references sonAdetTarihi via 'Son adet tarihinden' and does not elaborate on the optional referansTarih parameter. Baseline 3 is appropriate when schema does the heavy lifting.

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?

The description states a specific verb 'hesaplar' (calculates) and resource 'gebelik haftasını, trimesteri ve tahmini doğum tarihini' (pregnancy week, trimester, estimated due date), and specifies the input source 'Son adet tarihinden' (from last menstrual date). This clearly distinguishes it from sibling calculators like tarih_farki_hesapla or gun_sayaci_hesapla.

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 specific domain (pregnancy calculation) but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites mentioned. The description simply states what it does, leaving the agent to infer appropriate use.

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