Skip to main content
Glama
Sign In
astromei-rokuyo

astromei-rokuyo

by astromei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

六曜を調べる

get_rokuyo
Read-onlyIdempotent

Retrieve Rokuyo, lunar month and day, Japanese reading, and customary time slots for a specified Japan-local date to interpret traditional calendar details.

Instructions

Get Rokuyo, lunar month/day, Japanese reading and customary time slots for one date.

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

Input Schema

NameRequiredDescriptionDefault
dateYesJapan-local Gregorian date (YYYY-MM-DD), supported 2025–2027.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description usefully lists the returned content, but says nothing about behavior outside the supported 2025–2027 range or about failure modes.

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?

A single front-loaded sentence with no filler; every clause (identifier, returned fields, single-date scope) carries information.

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 one-parameter read-only lookup with no output schema, enumerating the returned fields is enough to call it correctly. Only edge-case handling for unsupported dates is unaddressed.

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?

Only one parameter, and the schema documents it fully at 100% coverage including the YYYY-MM-DD pattern and the 2025–2027 support window. The description adds no meaning beyond the schema, so the baseline 3 applies.

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?

A specific verb ('Get') and resource ('Rokuyo') followed by an enumeration of what is returned: lunar month/day, Japanese reading, and customary time slots. The phrase 'for one date' implicitly separates it from get_rokuyo_month and find_rokuyo_dates, but no sibling is named outright.

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 scope 'for one date' hints that month-range or date-search queries belong to the siblings, but there is no explicit when-to-use/when-not statement and no named alternative.

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