Zero-signup business-day date-math API: add days, count days between dates, is-business-day.
Business-day date math. Three modes inferred from params: add (start+days -> the date N business days away, negative days = before), diff (start+end -> count of business days between, inclusive of both endpoints), is (date -> is it a business day). Optional weekend (default sat,sun) and holidays (comma list of YYYY-MM-DD you supply). No signup, no API key. Pure UTC date-only math; no time-of-day/DST/timezone.
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | End date YYYY-MM-DD (diff mode) | |
| date | No | Date YYYY-MM-DD to test (is mode) | |
| days | No | Business days to add (add mode); negative subtracts | |
| start | No | Start date YYYY-MM-DD (add & diff modes) | |
| weekend | No | Comma list of weekend days, e.g. "sat,sun" (default sat,sun) | |
| holidays | No | Comma list of YYYY-MM-DD dates treated as non-working |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description discloses crucial behavioral details: 'Pure UTC date-only math; no time-of-day/DST/timezone' clarifies timezone handling, 'inclusive of both endpoints' specifies diff semantics, 'negative days = before' explains subtraction behavior, and 'No signup, no API key' sets expectations for auth. These are significant behavioral traits not covered by annotations. No contradiction with annotations exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a compact three-sentence structure that is front-loaded with the main purpose ('Business-day date math'), then expands with mode details and context. Every sentence contributes essential information—mode logic, optional parameters, and operational constraints—with no filler or repetition. It is appropriately sized for the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 6 parameters, no output schema, and no siblings, the description is remarkably complete. It explains what each mode returns (date, count, boolean), how to handle optional parameters, and edge cases like negative days and inclusive endpoints. It also addresses operational context (no auth, UTC-only) and parameter combinations. No significant gaps remain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although the input schema already describes each parameter at 100% coverage, the description adds substantial meaning by explaining how parameters combine into modes, the default weekend ('default sat,sun'), the holiday format ('comma list of YYYY-MM-DD'), and the inclusive diff behavior. This goes far beyond the schema's individual field descriptions and clarifies the inter-parameter logic.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool performs 'Business-day date math' and explicitly enumerates three distinct modes (add, diff, is) with input-output mappings. This is a specific verb+resource definition that fully clarifies what the tool does. Although there are no sibling tools to differentiate from, the description is unambiguous and comprehensive.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit when-to-use guidance for each mode: 'add (start+days -> the date N business days away, negative days = before)' describes when to use add; 'diff (start+end -> count of business days between...)' describes diff; 'is (date -> is it a business day)' describes is. It also explains optional parameters and defaults ('weekend (default sat,sun)'), giving clear context for invocation. No alternatives are needed since there are no siblings, but the mode descriptions function as clear usage rules.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
businessdaysClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Business-day, SLA, cron and recurrence calculations — offline, holiday-aware, no network.
Deterministic date arithmetic with auditable receipts: business days, due dates, holidays.
Date arithmetic: day differences, business days, age, leap years, day-of-week, add/subtract.
Public holiday data for 30+ countries. Check holidays, working days and calendars via AI assistants.
Add one secure layer between your agents and this server.
Only one tool exists, so there is no possibility of confusing it with another tool. The tool's purpose is clearly described.
The single tool name 'businessdays' is descriptive and consistent with the server's purpose. There are no mixed conventions to criticize.
With only one tool, the server is minimal, but for the narrow domain of business-day calculations it covers the necessary functionality. This is slightly under the typical 3-15 range but still reasonable.
The tool supports add, diff, and is modes, which cover the core operations for business-day math. It also allows configurable weekends and holidays, making it a complete solution for its stated purpose.
