moonlight-garden-handytools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOONLIGHT_GARDEN_MCP_URL | Yes | Required. The Moonlight Garden MCP address. Public addresses must use HTTPS. | |
| MOONLIGHT_GARDEN_MCP_TOKEN | No | Optional. Bearer token for the connection, if required. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| daily_routineC | Manually run three garden jobs, buy 10 bread worms, cast 10 times, and optionally fetch the latest recipe top five plus update the local ledger. Unknown action outcomes stop safely. The Agent must not choose a recovery option without the user's explicit decision. |
| farm_briefA | Read and compress farm, watering, chicken, cabbage-gap, bee-hive, bee-trip, and waiting-young state. It performs no garden or bee actions and returns UTC timestamps. |
| recipe_checkA | Validate and rank cookable ledger recipes using live inventory and quota. It never cooks or sells, but the upstream inventory list may auto-claim pending gifts; claimed gifts are returned with a UTC receipt time. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
daily_routine is clearly the action-oriented tool, farm_brief is the read-only status tool, and recipe_check is the recipe-analysis tool. The main ambiguity is that daily_routine also optionally fetches recipe top five and updates the ledger, which slightly overlaps with recipe_check's recipe/ledger focus.
All names use lowercase snake_case and are readable, but they do not follow a consistent verb_noun or noun_verb pattern. daily_routine and farm_brief are noun phrases while recipe_check reads as an object-verb, so the convention is mixed though still understandable.
Three tools is at the low end of the ideal range but each tool covers a distinct area: daily execution, status reporting, and recipe validation. The count is slightly small because daily_routine bundles several unrelated actions, but it is still reasonable for a 'handy tools' server.
The set covers the main daily-routine, status, and recipe-checking workflows, but it lacks targeted action tools for many states that farm_brief reports (watering, chickens, bees) and explicitly cannot cook or sell recipes. This leaves notable dead ends, though the core workflow is usable.