tilwhen date engine

Days between two dates

days_between

Read-onlyIdempotent

Signed whole calendar days from one date to another, midnight to midnight, endpoints exclusive (the gap).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	Yes
`tz`	No	IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC.	UTC
`from`	Yes	ISO date YYYY-MM-DD, or "today" (resolved in tz)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`answer`	Yes	The calculated answer (kind-discriminated)
`receipt`	Yes	Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID

TDQS

A4.5/5.0

Behavior5/5

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

The description adds behavioral details beyond annotations: 'signed', 'midnight to midnight', 'endpoints exclusive'. Annotations already indicate read-only, idempotent, non-destructive; description enriches with exact calculation semantics. No contradiction.

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?

Single sentence, no redundancy, every word adds value. Front-loaded with key action and semantics.

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?

With annotation coverage (readOnly, idempotent, non-destructive) and output schema (present), the description fully explains behavior. No gaps remain.

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 descriptions cover 67% of parameters (from, tz; to is referenced). The tool description does not add parameter-level meaning beyond the schema, so baseline 3 applies. No extra semantics needed given schema coverage.

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?

The description clearly states the tool computes signed whole calendar days between two dates, specifying 'midnight to midnight, endpoints exclusive (the gap)'. This uniquely identifies its purpose and distinguishes it from sibling tools like business_days or add_days.

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?

The description implies usage for calculating date differences, but does not explicitly state when to use this tool over alternatives. The context from sibling tools (e.g., business_days for business day counts) provides implicit guidance, but lacks explicit exclusions.

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

All tilwhen date engine tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct date operation: calendar addition/subtraction, business days, days between, holidays, invoice due, next occurrence, natural language parsing, and an explainer. No two tools overlap in purpose; descriptions clearly differentiate them.

Naming Consistency5/5

All tool names follow a consistent pattern: lowercase with underscores, predominantly verb_noun (add_days, parse_date_query) or noun_phrase (business_days, invoice_due). The naming is uniform and predictable.

Tool Count5/5

With 9 tools, the server is well-scoped. Each tool addresses a core date calculation need without redundancy or bloat. The count is appropriate for a focused date engine.

Completeness5/5

The tool surface covers all essential date operations: calendar arithmetic, business days, holidays, payment terms, next occurrences, and natural language queries. No obvious gaps remain for common date calculations.

Resources

Need Help?