Skip to main content
Glama
astromei-rokuyo

astromei-rokuyo

by astromei

月の六曜カレンダー

get_rokuyo_month
Read-onlyIdempotent

Retrieve the Rokuyo calendar for a selected Gregorian month from 2025 to 2027 to view daily Rokuyo labels in one offline result.

Instructions

Get the Rokuyo calendar for one Gregorian month (2025–2027).

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": {
      "year": "<year>",
      "month": "<month>"
    },
    "name": "get_rokuyo_month"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
monthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds the Gregorian-month scope and 2025–2027 range, but does not explain output format or edge behavior; with annotations present, this is adequate but not rich.

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 states the action, output, scope, and supported range efficiently.

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

Completeness3/5

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

For a simple read-only tool with two parameters and annotations, the definition covers the essential scope and year range. However, with no output schema, it gives only minimal indication of what the returned calendar contains beyond the term 'Rokuyo calendar'.

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 0%, but there are only two simple bounded integers. The description clarifies that the month is Gregorian and the supported year range is 2025–2027, though it does not state the month numbering or that both parameters are required; the schema itself carries required/min/max.

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 verb and resource: 'Get the Rokuyo calendar' for 'one Gregorian month'. The month scope is clear, but it does not explicitly distinguish itself from siblings like get_rokuyo or find_rokuyo_dates.

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?

It describes what the tool returns but gives no explicit when-to-use guidance, exclusions, or alternatives. The monthly scope implies appropriate usage, but routing among the sibling tools is left to inference.

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