Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

date_calc

Add or subtract days and months from a date and return the result with weekday, day-of-year and ISO week. Pure CPU, instant.

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

Input Schema

NameRequiredDescriptionDefault
dateYesStart date (default today)
daysNoDays to add or subtract
monthsNoMonths to add or subtract

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed4 schema fields changed
    • addedInput schema / properties / date
      Added value: +{
+  "description": "Start date (default today)",
+  "type": "string"
+}
    • addedInput schema / properties / days
      Added value: +{
+  "description": "Days to add or subtract",
+  "type": "integer"
+}
    • addedInput schema / properties / months
      Added value: +{
+  "description": "Months to add or subtract",
+  "type": "integer"
+}
    • addedInput schema / required
      Added value: +[
+  "date"
+]
  4. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful traits: pure CPU, no external calls, instant response, and the shape of the returned data. However, it is silent on the behaviors most likely to bite — month-end clamping (e.g. Jan 31 + 1 month), timezone/DST handling, and whether negative values are the only way to subtract. Those are material gaps for a date-arithmetic tool.

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?

Two tight sentences with zero filler: the operation and return payload come first, then a single performance note. Nothing is redundant or buried.

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?

For a simple three-parameter CPU tool with no output schema, the description covers the operation and enumerates return fields, which is most of what an agent needs. The missing piece is edge-case behavior around month arithmetic and timezone assumptions, which matters given no annotations or output schema to fall back on.

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%, so the baseline of 3 applies and the schema already documents date, days, and months including the today-default. The description adds no syntax, format, or sign conventions beyond what the schema states.

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 set (add/subtract) and resource (days and months from a date) and names the output fields (weekday, day-of-year, ISO week). An agent can grasp the operation immediately. It does not differentiate from related siblings like business_days, week_number, or convert_timestamp, which is the only thing keeping it from a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named even though business_days, week_number, and convert_timestamp overlap conceptually. The only usage-adjacent signal is 'Pure CPU, instant,' which hints at a local computation but is a performance note rather than routing guidance.

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

All GadgetHumans API Hub 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