Skip to main content
Glama

Akan day names for a weekday

day_names.for_weekday
Read-only

Use this when someone already knows the weekday and asks for the Akan day names for it (for example "what are the Akan names for someone born on a Friday"), or asks what weekday an Akan day name such as Kofi or Akosua belongs to. Do not use it when a date of birth is given: use day_names.for_date so the weekday is worked out.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "day_names.for_weekday"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexNoLeave out to get both.
nameNoAn Akan day name to look up instead, for example "Kofi" or "Akosua".
weekdayNoThe weekday in English.

Output Schema

NameRequiredDescriptionDefault
maleNo
noteYes
femaleNo
weekdayYes
akan_dayYes
appellationNo
explore_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: the tool works bidirectionally, and the reverse lookup of a name is a supported mode rather than an error. It does not state what happens if both weekday and name are supplied, nor what the response contains, but an output schema exists to cover the latter.

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: usage and examples first, the exclusion and redirect second. Every clause carries selection-relevant information, and the front-loading puts the primary trigger before the routing caveat.

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?

With annotations, a full-coverage schema, and an output schema, the description is nearly complete for a two-mode lookup tool. The one untold case is conflict/empty input — all three parameters are optional and nothing says what happens if both weekday and name are passed, or if neither is.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: it establishes that name and weekday are alternative lookups rather than complementary filters ("instead"), which the schema's three-optional-parameter shape alone does not make obvious. The sex parameter's default behavior is left to the schema's own description.

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 (look up Akan day names) and resource (a weekday, or an Akan day name), and explicitly contrasts with the sibling day_names.for_date. The two supported directions (weekday→names, name→weekday) are spelled out, so an agent can distinguish it from the date-based sibling without opening either schema.

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 an example utterance ("what are the Akan names for someone born on a Friday"), an explicit second trigger (reverse lookup of Kofi/Akosua), and an explicit exclusion plus the named alternative (use day_names.for_date when a birth date is given). Nothing is left to inference about tool selection.

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