Skip to main content
Glama
Sign In
astromei-rokuyo

astromei-rokuyo

by astromei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

大安・友引などの日を探す

find_rokuyo_dates
Read-onlyIdempotent

Searches an inclusive Japan-local date range of up to 366 days to return dates matching a chosen Rokuyo label.

Instructions

Find a chosen Rokuyo label in an inclusive range of at most 366 days. Does not evaluate other almanac annotations.

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

Input Schema

NameRequiredDescriptionDefault
endYesJapan-local Gregorian date (YYYY-MM-DD), supported 2025–2027.
startYesJapan-local Gregorian date (YYYY-MM-DD), supported 2025–2027.
rokuyoNo大安

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the bar is lower. The description still adds real context beyond them: a hard 366-day inclusive-range constraint and an explicit statement that other almanac annotations are not evaluated. It stops short of saying what happens when the range or date bounds are violated.

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?

Two short sentences, front-loaded with the core action and range constraint, and the second sentence is a genuine scope exclusion rather than filler. Nothing could be cut without losing 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 read-only lookup with rich annotations and no output schema, the description covers the key constraint (range length) and scope. Only the failure behavior for out-of-range dates or overflowing ranges is left unstated.

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 coverage is 67%, with the rokuyo enum (six labels, default 大安) and both date parameters documented in the schema. The description only echoes 'a chosen Rokuyo label' and adds no format or default detail, so it does not compensate for the remaining coverage gap.

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?

States a specific verb and resource: finding a chosen Rokuyo label within an inclusive date range, plus a clear scope exclusion ('Does not evaluate other almanac annotations'). This separates it in spirit from get_rokuyo and get_rokuyo_month (range search vs. single-date/month views), though no sibling is named explicitly.

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?

Usage is implied by the range-search framing and the 366-day cap, but there is no explicit 'use this when... instead of get_rokuyo/get_rokuyo_month' guidance, nor any statement about invalid ranges or dates outside 2025-2027.

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