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

jp-business-calendar-mcp

by panda-studio-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

business_days_between

Count business days between two dates, inclusive, using Japanese calendar data.

Instructions

start〜end（両端含む）の営業日数を数える。

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": "<start>",
      "end": "<end>"
    },
    "name": "business_days_between"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 inclusive business days but fails to define what constitutes a business day (e.g., weekends, holidays). It lacks details on return values, edge cases, or dependencies.

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 concise sentence in Japanese with no redundant words. It is front-loaded with the core action. However, over-conciseness sacrifices completeness.

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

Completeness1/5

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

Given no annotations, no output schema, and 0% schema coverage, the description is severely incomplete. It omits crucial context such as date format, holiday calendar, behavior for invalid dates, and return type. The tool is under-specified for an agent to use correctly.

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 description coverage is 0%, and the description adds minimal meaning beyond parameter names. It implies 'start' and 'end' are date strings but does not specify format or constraints. The description does not compensate for the absence of schema descriptions.

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 it counts business days between start and end inclusive. It distinguishes from sibling tools like 'days_until' (counts days to a future date) and 'is_holiday' (checks if a date is a holiday).

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention scenarios where other tools like 'days_until' or 'next_business_day' would be more appropriate.

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