Skip to main content
Glama
Sign In
jp-business-calendar-mcp

jp-business-calendar-mcp

by panda-studio-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

days_until

Calculate remaining calendar or business days to a target date for deadline management. Defaults to today when no base date is specified.

Instructions

指定日までの残り日数・営業日数（締切管理用）。base 省略時は今日。

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

Input Schema

NameRequiredDescriptionDefault
baseNo
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description must fully disclose behavior. It mentions counting days and business days, but omits crucial details: what happens when the target date is in the past (returns negative?), the definition of business days (uses a holiday calendar?), and any side effects. This lack of transparency could confuse the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that front-loads the purpose. It is efficient but could briefly mention parameter formats without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and annotations, the description should provide more context about return values (e.g., integer, units) and edge cases (e.g., past dates). The current description is too minimal for an agent to use confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% with two parameters. The description clarifies that 'base' defaults to today, but it does not specify the required date format (e.g., YYYY-MM-DD) or any constraints. The compensation is partial, leaving ambiguity for the agent.

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 remaining days or business days until a specified date, specifically for deadline management. It mentions the base parameter defaults to today, which distinguishes it from siblings like business_days_between that count days between two dates.

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 provides context for deadline management and explains base default behavior, but it does not explicitly tell when to use this tool versus alternatives (e.g., business_days_between for general date differences). The guidance is implied but lacks clear exclusions.

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

Deploy Server

Other Tools