Microapp

days-between

Read-onlyIdempotent

Calculate the number of days between two ISO 8601 dates. Returns days, weeks, months, and years (decimal). Inclusive count = absolute |end - start|.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`end`	Yes	End date in ISO 8601 (YYYY-MM-DD or full ISO timestamp).
`start`	Yes	Start date in ISO 8601 (YYYY-MM-DD or full ISO timestamp).

Output Schema

TableJSON Schema

Name	Required	Description
`days`	Yes	Number of days between the dates (absolute).
`weeks`	Yes	Equivalent number of weeks.
`years`	Yes	Approximate number of years (assuming 365.25 days/year).
`months`	Yes	Approximate number of months (assuming 30.4375 days/month).
`direction`	Yes	Whether end comes after or before start.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedMay 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the tool is known to be safe and non-mutating. The description adds valuable behavior details: the inclusive count formula using absolute difference and the multi-unit return values. This goes beyond annotations and clarifies the calculation method.

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?

The description is three short sentences, front-loaded with the primary purpose, then giving essential behavioral details. Every sentence earns its place, with no repetition or wordiness.

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?

For a simple read-only calculator with a schema covering both parameters and an output schema present, the description provides sufficient context: purpose, return units, and calculation logic. The annotations cover safety, so no additional behavioral caveats are needed.

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?

The input schema already provides full descriptions for both 'start' and 'end' parameters (ISO 8601 format), so schema coverage is 100%. The description does not add significant parameter-level meaning, though the absolute-difference formula implicitly states that parameter order is irrelevant.

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 calculates the number of days between two ISO 8601 dates, with a specific verb and resource. It also notes the returned units (days, weeks, months, years), distinguishing it from other date-related calculators in the sibling list like 'easter-date-calculator' or 'age-on-other-planets'.

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?

The description implies when to use it (when you need the time span between two dates) but does not explicitly state alternatives or exclusions. There is no mention of when not to use it or which sibling tool might be more appropriate in other scenarios.

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

All Microapp 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

A3.9/5.0

Disambiguation4/5

Most tools have distinct purposes. However, 'hex-to-rgb' is redundant with 'color-converter', which already handles hex-to-RGB conversion, causing potential confusion.

Naming Consistency4/5

Names follow a consistent lowercase-with-hyphens style, but vary in pattern (e.g., 'angle-converter', 'average-calculator', 'dedup-lines'). One tool ('internal-do-not-call') deviates from the descriptive norm.

Tool Count2/5

With 46 tools, the server is heavily populated. Many converters could be merged into a generic unit converter, and there is redundancy, making the surface unnecessarily large for a single server.

Completeness4/5

The server covers a broad range of utility domains: converters, text processing, math, cryptography, etc. Minor redundancies exist (e.g., hex-to-rgb vs color-converter), but the set is otherwise comprehensive.

Resources

Need Help?