Skip to main content
Glama

afrim_geez_numeral

Converts positive integers up to 13 digits into Ge'ez numerals, enabling Ethiopian script representation for numbers in text or applications.

Instructions

Write a positive integer (up to 13 digits) with Ge'ez numerals, e.g. 1966 -> ፲፱፻፷፮, 10000 -> ፼, 2018 -> ፳፻፲፰.

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": {
      "number": "<number>"
    },
    "name": "afrim_geez_numeral"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key domain constraint: input must be a positive integer of at most 13 digits, with sample outputs showing the numeral mapping. It does not state what happens for out-of-range or invalid input (negative, zero, >13 digits), which is the main behavioral unknown. The operation is evidently a pure computation with no side effects, but that is inferred rather than declared.

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?

One sentence, front-loaded with the operation and its constraint, followed by compact inline examples that demonstrate the format without prose. Nothing is wasted and the special case (10000 -> ፼) is shown rather than explained.

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?

An output schema exists, so return values need no explanation, and the description covers the single input's domain. For a one-parameter pure conversion tool this is nearly complete; only error/edge-case behavior for invalid input is left unstated.

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% — the only parameter is titled 'Number' with no description, so the description must compensate and largely does, adding both the positivity requirement and the 13-digit upper bound that the bare integer schema lacks. It still doesn't clarify edge cases such as zero or leading-zero handling, keeping it below a 5.

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 gives a specific verb and resource: writing a positive integer in Ge'ez numerals, with the range constraint (up to 13 digits) stated up front. The three worked examples (1966 -> ፲፱፻፷፮, 10000 -> ፼, 2018 -> ፳፻፲፰) make the transformation unambiguous. It does not explicitly distinguish itself from siblings like afrim_transliterate, but no sibling obviously overlaps, so the gap is minor.

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 rather than stated: the examples show this is the tool for rendering a numeric value in Ge'ez script, and the 13-digit limit hints at scope. There is no explicit when-to-use or when-not-to-use statement, and no mention of when to prefer afrim_transliterate or afrim_lookup instead.

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