Calcgrid

Add Ghana Working Days

add_gh_working_days

Read-onlyIdempotent

Use this when you need a deterministic Ghana working-day offset. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery.

Do not use this when this package covers the nationwide statutory/public-holiday layer only. It is not a universal private-employer, bank, exchange, school, local, sector or essential-service calendar. The 2026 package uses observed dates published or cross-checked for 2026; lunar dates and later Executive Instruments may change. It does not treat the pre-Act-1142 4 August Founder’s Day or 2025-era September naming as current law, and it does not infer additional closure days from the legal anchors alone. What it computes: Adds or subtracts Ghana authority-scope working days in exact coverage. Example user requests: Add or subtract Ghana working days around Republic Day observed. | Add or subtract Ghana working days around Ordinary Ghana working day. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/ghana-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/ghana-public-add-working-days.md

Input Schema

TableJSON Schema

Name	Required	Description	Default
`start_date`	Yes	Gregorian start date in 2026-2026.
`working_days`	Yes	Signed offset; start date excluded for non-zero offsets.

Output Schema

TableJSON Schema

Name	Required	Description
`links`	No
`result`	Yes
`request`	Yes
`sources`	No
`success`	Yes
`version`	No
`freshness`	No
`timestamp`	Yes
`next_actions`	No
`service_version`	Yes	Deployed Calcgrid implementation version used for the result.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: nationwide statutory layer only, 2026 observed-date dataset, lunar dates and later Executive Instruments may change, and pre-Act-1142 Founder's Day is excluded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the when-to-use condition, which is good, but several sentences restate the same idea ('Adds or subtracts... in exact coverage' repeats the opening), the example user requests are low-value, and the formula is duplicated across the description. The REST fallback and docs URL earn their place; the redundancy does not.

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?

Output schema exists, so the enumerated output fields are redundant but harmless. Everything an agent needs to call correctly — scope limits, date window, formula, fallback endpoint — is present, missing only explicit sibling differentiation against count_/check_ variants.

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% for both parameters, so baseline 3 applies. The description lists the inputs and a JSON example but adds no semantics beyond the schema's own field descriptions ('signed offset', date range).

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?

States a specific verb (add/subtract) and resource (Ghana working days) plus the exact scope: 'deterministic Ghana working-day offset'. An agent can distinguish this from count_gh_working_days and check_gh_working_day by the offset semantics, though neither sibling is named explicitly.

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?

Gives explicit 'Use this when...' and 'Do not use this when...' clauses plus a directive to call the tool rather than compute from memory. The exclusions are real (private-employer, bank, exchange, school calendars are out of scope), but the negative clause is grammatically mangled ('Do not use this when this package covers...'), which weakens routing precision.

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

All Calcgrid tools Inspect

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

Need Help?