Skip to main content
Glama

Akan day name for a birth date

day_names.for_date
Read-only

Use this when someone gives a date of birth and asks for their Akan or Ghanaian day name (for example "what is my Ghanaian name, I was born on 6 March 1994"), or asks what day name a baby born on a date would have. It works out the weekday itself; do not guess the weekday first. Do not use it for names from other naming traditions, for the meaning of a surname, or for horoscopes.

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": {
      "date_of_birth": "<date_of_birth>"
    },
    "name": "day_names.for_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexNoLeave out to get both the girl's and the boy's name.
date_of_birthYesThe date of birth as YYYY-MM-DD, for example 1994-03-06.

Output Schema

NameRequiredDescriptionDefault
maleNo
noteYes
femaleNo
weekdayYes
akan_dayYes
appellationNo
explore_urlNo
date_of_birthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, so the bar is lower. The description adds meaningful behavioral context beyond them: the tool internally resolves the weekday, so the caller must not supply or guess one, and it clarifies the excluded domains. It does not describe the response shape, but an output schema exists to cover that.

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?

One compact paragraph that front-loads the primary trigger before the example, mechanism note, and exclusions. Every sentence carries routing value, though the parenthetical example is slightly long relative to the rest.

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?

A simple two-parameter, read-only tool with an output schema and rich annotations needs little more than what is here: triggers, exclusions, and the weekday-resolution caveat are all present. Only a note on how the two names are returned when sex is omitted would make it fully self-contained, and the schema already implies that.

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 100%, so the schema already documents both date_of_birth format and the sex enum including the both-names default. The description adds no format or semantics beyond the schema; its example date is written in natural language ("6 March 1994") rather than the required YYYY-MM-DD, so it neither compensates nor misleads, leaving this at the baseline.

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?

States a specific verb and resource: it derives an Akan/Ghanaian day name from a date of birth, including the baby-name use case. It also carves itself away from the sibling by noting it computes the weekday itself, so an agent can distinguish it from day_names.for_weekday without inspecting schemas.

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

Usage Guidelines5/5

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

Gives an explicit trigger with a concrete user utterance ("what is my Ghanaian name, I was born on 6 March 1994"), a secondary trigger for babies, and explicit exclusions: other naming traditions, surname meanings, horoscopes. It also instructs the agent not to pre-compute the weekday, which is the key routing rule against the sibling.

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