Skip to main content
Glama
Sign In

Exepal

by com.exepal
OverviewDiscussionsAdmin

Nepali date converter (Bikram Sambat)

south_asia_date
Read-onlyIdempotent

Bikram Sambat (Nepali) <-> Gregorian date conversion with weekday, Nepali month names, Devanagari digits and Nepal fiscal year. Use for any Nepali (BS / Bikram Sambat / Vikram Samvat) date: converting to or from AD, finding the weekday, writing it in Nepali, or finding the Nepal fiscal year. Models often get BS dates wrong; this is an exact table (1970-2090 BS). Returns bs {iso, text, textNe, monthName, daysInMonth}, ad {iso}, weekday, weekdayNe, fiscalYear and isSaturday. Price: $0.001 per call from Exepal credit; not charged if the call fails. Includes free daily calls.

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": "south_asia_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesA date: 2083-01-15, 15-01-2083, '15 Baisakh 2083' or '१५ बैशाख २०८३'. Supported 1970-2090 BS / 1913-2034 AD
fromNoCalendar of the input. auto (default): Devanagari digits, Nepali month names or a year above 2034 mean BS; otherwise AD is assumed

Output Schema

NameRequiredDescriptionDefault
adNo
bsNo
fromNoCalendar the input was read as: bs or ad
inputNo
assumedNoTrue when the year fit both calendars and AD was assumed; send from to be explicit
weekdayNo
weekdayNeNo
fiscalYearNoNepal fiscal year, e.g. 2082/83
isSaturdayNoSaturday is Nepal's weekly public holiday
supportedRangeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "ad": {
+      "properties": {
+        "day": {
+          "type": "number"
+        },
+        "iso": {
+          "description": "YYYY-MM-DD Gregorian",
+          "type": "string"
+        },
+        "month": {
+          "type": "number"
+        },
+        "year": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "assumed": {
+      "description": "True when the year fit both calendars and AD was assumed; send from to be explicit",
+      "type": "boolean"
+    },
+    "bs": {
+      "properties": {
+        "day": {
+          "type": "number"
+        },
+        "dayOfYear": {
+          "type": "number"
+        },
+        "daysInMonth": {
+          "type": "number"
+        },
+        "daysInYear": {
+          "type": "number"
+        },
+        "iso": {
+          "description": "YYYY-MM-DD in Bikram Sambat",
+          "type": "string"
+        },
+        "month": {
+          "type": "number"
+        },
+        "monthName": {
+          "type": "string"
+        },
+        "monthNameNe": {
+          "type": "string"
+        },
+        "ne": {
+          "description": "Date in Devanagari digits",
+          "type": "string"
+        },
+        "text": {
+          "description": "e.g. 15 Baisakh 2083",
+          "type": "string"
+        },
+        "textNe": {
+          "type": "string"
+        },
+        "year": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "fiscalYear": {
+      "description": "Nepal fiscal year, e.g. 2082/83",
+      "type": "string"
+    },
+    "from": {
+      "description": "Calendar the input was read as: bs or ad",
+      "type": "string"
+    },
+    "input": {
+      "type": "string"
+    },
+    "isSaturday": {
+      "description": "Saturday is Nepal's weekly public holiday",
+      "type": "boolean"
+    },
+    "supportedRange": {
+      "properties": {
+        "ad": {
+          "type": "string"
+        },
+        "bs": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "weekday": {
+      "type": "string"
+    },
+    "weekdayNe": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the authoritative data range (1970-2090 BS), warns that models commonly get BS dates wrong and that this is an exact table, and lists the concrete return fields. It also states cost behaviour ($0.001 per call, free if the call fails, plus free daily calls), which no annotation conveys.

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?

Front-loads purpose and usage in the first two sentences, then tucks capability claims, return shape, and pricing after. It is dense but mostly earns its space; the enumerated return fields are somewhat redundant given an output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, trigger conditions, input format breadth, authoritative range, cost, and failure-charging semantics — everything an agent needs to decide and invoke. With an output schema present, expanded return-value documentation is not required, so no meaningful gap remains.

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%, with the `date` format examples and the supported range already documented in the schema, so the baseline of 3 applies. The description's mention of 'Devanagari digits, Nepali month names' implicitly reinforces the auto-detection logic but adds no new syntax or constraint beyond the schema.

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+resource in the first clause: 'Bikram Sambat (Nepali) <-> Gregorian date conversion', and enumerates the derived outputs (weekday, Nepali month names, Devanagari digits, fiscal year). The subject matter is unmistakably distinct from siblings like south_asia_forex or south_asia_phone, so an agent can route without opening the schema.

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

Usage Guidelines4/5

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

'Use for any Nepali (BS / Bikram Sambat / Vikram Samvat) date: converting to or from AD, finding the weekday, writing it in Nepali, or finding the Nepal fiscal year' gives clear triggering conditions with aliases an agent may encounter in user text. It does not name an explicit alternative or a when-not-to-use case, which keeps it just short of a 5.

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

All Exepal toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources