Retrieve the current Stardew Valley in-game date, season, and weekday to plan farming, events, and villager schedules without checking the calendar manually.
获取游戏内当前日期、季节和星期信息。
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the returned information types (date, season, day-of-week), which is useful behavioral context. It still doesn't mention whether the result is cached or reflects a specific game state, but for a simple read-only query this is reasonably transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence that delivers all necessary information without any filler or redundancy. It's appropriately sized for a zero-parameter query tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that there is an output schema (which likely documents the return fields) and no parameters, the description is nearly complete. It clearly states what is retrieved, though it doesn't explicitly note the read-only nature or that the output schema defines the exact structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, so parameter semantics is not applicable and the baseline is 4. The description properly avoids discussing parameters and focuses on the output instead.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb+resource: it retrieves the in-game current date, season, and day-of-week. This clearly distinguishes it from siblings like get_todays_events or get_month_calendar, which focus on events or calendars rather than raw date/time state.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied: use this when you need the current in-game temporal context. However, the description provides no explicit when-to-use guidance, no exclusions, and no named alternatives, leaving the agent to infer that get_todays_events is for events rather than the base date.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.