Scientific Calculator

Days Calculator

calculator_days

Read-only

Add or subtract a number of days from a starting date (handles leap years).

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": {
      "start_date": "<start_date>",
      "days": "<days>",
      "operation": "<operation>"
    },
    "name": "calculator_days"
  }
}

Input Schema

Name	Required	Description
`days`	Yes	Number of days to add or subtract.
`operation`	Yes	add or subtract.
`start_date`	Yes	Starting date.

Output Schema

Name	Required	Description	Default
`weekday`	No
`expression`	Yes
`result_date`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, closed-world calculation. The description adds a relevant behavioral detail beyond the annotations: leap years are handled explicitly, which matters for date arithmetic correctness.

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 a single front-loaded sentence with no wasted wording. It leads with the operation and includes the key leap-year nuance efficiently.

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 pure-calculation tool with annotations and an output schema, the description covers the core operation and a meaningful edge-case behavior. The main remaining gap is lack of sibling differentiation, which is a usage-guidance concern rather than a missing detail for invocation.

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%, and the schema already documents start_date, days, and operation with examples. The description only implies those concepts generically and does not add format or constraint details beyond what the schema provides.

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?

The description states a specific operation (add or subtract days) on a specific input (a starting date), so an agent can understand the tool without opening the schema. It does not explicitly distinguish itself from sibling date tools such as calculator_date_difference or calculator_weekday.

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 intended use is implied clearly by the name and description, but there is no explicit when-to-use or when-not-to-use guidance. With many sibling date/calendar tools available, naming an alternative such as calculator_date_difference would make selection more reliable.

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

All Scientific Calculator 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.