Skip to main content
Glama

afrim_ethiopian_date

Convert dates between the Gregorian and Ethiopian calendars to get both dates, Ethiopian month names, Ge'ez year numerals, and formatted date strings for records, localization, or scheduling.

Instructions

Convert a date between the Gregorian and the Ethiopian calendar. date: DD/MM/YYYY, DD.MM.YYYY, DD-MM-YYYY (2-digit years are 20YY) or YYYY-MM-DD. calendar_of_input: 'gregorian' (default) or 'ethiopian'. Returns both dates, the Ethiopian month name, the year in Ge'ez numerals, and formatted strings such as '6 ሕዳር 2019' and 'ሕዳር 6 ቀን 2019 ዓ.ም.'.

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": "<date>"
    },
    "name": "afrim_ethiopian_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
calendar_of_inputNogregorian

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries full disclosure burden and does well: it names accepted input formats, the default calendar, and enumerates what comes back (both dates, Ethiopian month name, Ge'ez numerals, formatted strings). It omits failure behavior for invalid or ambiguous dates, which is the main remaining gap.

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?

Purpose is front-loaded in the first sentence, followed by format and return details in a compact block. Dense and largely waste-free, though the line-broken format rules read as slightly cramped.

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 only two parameters and an output schema already present, the description covers what the schema cannot: input syntax, defaults, and the shape of results. Only edge-case handling (invalid dates, format ambiguity) is missing, which is minor for a pure conversion utility.

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 0%, so the description must supply all parameter meaning, and it does: three accepted date syntaxes plus ISO, the 2-digit-year rule ('20YY'), and the two allowed values of calendar_of_input with its default. Some ambiguity about how conflicting formats are resolved when a string could parse more than one way is left unaddressed.

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: "Convert a date between the Gregorian and the Ethiopian calendar." This clearly distinguishes it from siblings like afrim_geez_numeral or afrim_transliterate, which handle numerals and script rather than calendar conversion.

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 tool's name and purpose, and the default ('gregorian') is stated, but there is no explicit when-to-use or when-not guidance and no reference to alternatives. For a single-purpose utility this is minimally adequate rather than exemplary.

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