Siltwell
Your garden notebook: ask about your beds, plantings, harvests and frost dates, and log your work.
Should I use this
Quality & Safety
Findings (1)
- LOWTool 'get_current_conditions' description lacks action verbin get_current_conditions
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"garden": {
"url": "https://app.siltwell.com/mcp"
}
}
}Remote endpoints
https://app.siltwell.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (32)
🟢query_plantings(garden, status, plant)
List the user's plantings (what is planted, where, when, how, current status). Use when the user asks what they planted, when something was sown/transplanted, or what's growing in a bed.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"status": {
"type": "string",
"enum": [
"active",
"finished",
"failed",
"all"
],
"description": "Default: active."
},
"plant": {
"type": "string",
"description": "Filter by plant common name (contains, case-insensitive)."
}
}
}🟢search_events(garden, type, plant, since, limit)
Search the garden log: watering, fertilizing, transplanting, pruning, pest sightings, treatments, frost damage, notes. Use when the user asks when they last did something or what happened in the garden.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"type": {
"type": "string",
"enum": [
"watered",
"fertilized",
"transplanted",
"pruned",
"pest",
"treated",
"frost_damage",
"note"
]
},
"plant": {
"type": "string",
"description": "Filter to events on plantings of this plant name."
},
"since": {
"type": "string",
"description": "ISO date lower bound (inclusive)."
},
"limit": {
"type": "number",
"description": "Max rows, default 50."
}
}
}🟢get_harvests(garden, since, plant)
List harvests with per-plant totals. Use when the user asks what/how much they harvested.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"since": {
"type": "string",
"description": "ISO date lower bound."
},
"plant": {
"type": "string"
}
}
}🟢list_beds(garden)
List the garden's beds: name, type (outdoor_bed/raised_bed/greenhouse/grow_light_shelf/pot), dimensions in cm, notes, and how many active plantings each holds. Use to see what beds exist and where there may be room.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
}
}
}🟢get_bed_layout(garden, bed)
Read a bed's layout grid: the bed's dimensions (cm) plus each placed planting's footprint (xCm, yCm from the bed's top-left; wCm × hCm), and any active plantings not yet placed. Use to reason about space — e.g. "is there 60 cm free at the front of Bed 2?". Positions are written by place_planting.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"bed": {
"type": "string",
"description": "Bed name."
}
},
"required": [
"bed"
]
}🟢get_current_conditions(garden)
Current weather at the garden (station if connected, else forecast) plus per-bed soil moisture/temperature. Use for "how is the garden right now / should I water".
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
}
}
}🟢get_soil_readings(garden)
Latest soil moisture % and soil temperature per bed, with bed names. Use for watering/sowing decisions.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
}
}
}🟢get_forecast(garden)
7-day forecast for the garden with overnight-low frost alerts. Use for planting timing, frost protection, watering plans.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
}
}
}🟢get_history(garden, since)
Daily weather history for the garden: min/max temp, rain, growing degree days (base 10 °C) with a cumulative total. Use for "how warm/wet has it been" and growth-progress questions.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"since": {
"type": "string",
"description": "ISO date, default 90 days ago."
}
}
}🟢get_plan(garden)
Upcoming sowing/transplant windows computed from the user's plant catalog and the garden's frost dates, plus zone, frost dates, and any due care tasks (watering/fertilizing, with a rain-skip hint). Use for "what should I plant/start/transplant and when" and "what care is due".
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
}
}
}⚪log_event(garden, type, plant, plantingId, bed, ...)
Record something the user did or observed: watered, fertilized, transplanted, pruned, pest sighting, treatment, frost damage, or a note. Attach it to a plant's active planting via `plant`, to a bed via `bed`, or garden-wide with neither. If both plant and bed are given, the event attaches to the plant's planting.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"type": {
"type": "string",
"enum": [
"watered",
"fertilized",
"transplanted",
"pruned",
"pest",
"treated",
"frost_damage",
"note"
]
},
"plant": {
"type": "string",
"description": "Plant name — targets its most recent active planting."
},
"plantingId": {
"type": "string",
"description": "Exact planting id (from query_plantings) — overrides plant."
},
"bed": {
"type": "string",
"description": "Bed name — for bed-level events."
},
"note": {
"type": "string"
},
"occurredAt": {
"type": "string",
"description": "ISO datetime; default now."
},
"pestName": {
"type": "string",
"description": "For type=pest."
},
"severity": {
"type": "string",
"enum": [
"low",
"medium",
"high"
],
"description": "For type=pest."
},
"product": {
"type": "string",
"description": "For fertilized/treated."
},
"amount": {
"type": "string",
"description": "For fertilized/treated."
}
},
"required": [
"type"
]
}⚪record_harvest(garden, plant, plantingId, quantity, unit, ...)
Record a harvest, e.g. "I picked 2 kg of cucumbers" or "2 lb of tomatoes". Resolves the plant's active planting automatically. Pounds and ounces are stored as grams.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"plant": {
"type": "string"
},
"plantingId": {
"type": "string"
},
"quantity": {
"type": "number"
},
"unit": {
"type": "string",
"enum": [
"g",
"kg",
"lb",
"oz",
"pcs"
]
},
"harvestedAt": {
"type": "string",
"description": "ISO datetime; default now."
},
"notes": {
"type": "string"
}
},
"required": [
"quantity",
"unit"
]
}🔴add_planting(garden, plant, bed, method, sownAt, ...)
Record that the user planted/sowed something: creates the plant in their catalog if new and the planting in the named bed. Passing variety replaces the variety stored on an existing plant with the same name.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"plant": {
"type": "string"
},
"bed": {
"type": "string"
},
"method": {
"type": "string",
"enum": [
"direct_seed",
"indoor_start",
"transplanted_seedling"
],
"description": "Default direct_seed."
},
"sownAt": {
"type": "string",
"description": "ISO date; default today."
},
"transplantedAt": {
"type": "string",
"description": "ISO date the seedling went into the bed (indoor starts)."
},
"variety": {
"type": "string",
"description": "Variety/cultivar, e.g. \"Sremski F1\". Stored on the plant; replaces the variety of an existing plant with the same name."
},
"quantity": {
"type": "number"
},
"notes": {
"type": "string"
}
},
"required": [
"plant",
"bed"
]
}⚪log_curing(garden, plantingId, kind)
Record that a harvested crop has finished curing (or dismiss the reminder). Use when the gardener says they've cured, dried, trimmed or stored a crop like garlic, onions or herbs.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"plantingId": {
"type": "string",
"description": "Exact planting id (from query_plantings or get_bed_layout)."
},
"kind": {
"type": "string",
"enum": [
"cured",
"dismissed"
]
}
},
"required": [
"plantingId",
"kind"
]
}🟡create_bed(garden, name, type, lengthCm, widthCm, ...)
Add a garden bed. `type` is one of outdoor_bed (in-ground), raised_bed, greenhouse, grow_light_shelf, pot. Dimensions (lengthCm/widthCm/heightCm) are optional. Use when the user wants a new bed or planting area.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"name": {
"type": "string"
},
"type": {
"type": "string",
"enum": [
"outdoor_bed",
"raised_bed",
"greenhouse",
"grow_light_shelf",
"pot"
]
},
"lengthCm": {
"type": "number",
"description": "Length in centimeters (optional)."
},
"widthCm": {
"type": "number",
"description": "Width in centimeters (optional)."
},
"heightCm": {
"type": "number",
"description": "Height/depth in centimeters (optional)."
}
},
"required": [
"name",
"type"
]
}🔴update_bed(garden, bed, name, type, lengthCm, ...)
Change an existing bed's name, type, or dimensions. Identify the bed by its current name. Use when the user wants to rename a bed, change its type, or set/adjust its dimensions.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"bed": {
"type": "string",
"description": "The bed's current name."
},
"name": {
"type": "string",
"description": "New name (optional)."
},
"type": {
"type": "string",
"enum": [
"outdoor_bed",
"raised_bed",
"greenhouse",
"grow_light_shelf",
"pot"
],
"description": "New type (optional)."
},
"lengthCm": {
"type": "number"
},
"widthCm": {
"type": "number"
},
"heightCm": {
"type": "number"
}
},
"required": [
"bed"
]
}🟡set_care_schedule(garden, plant, bed, type, everyDays, ...)
Create a recurring care schedule (water/fertilize/custom). Scope it to a plant (its active planting), a bed, or the whole garden. Recurrence is EITHER everyDays (e.g. 3) OR weekdays (e.g. ['monday','thursday']). Use when the user wants a repeating watering/feeding reminder. Optionally end it on a date (endsOn) or after N completions (endsAfter); use at most one.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"plant": {
"type": "string",
"description": "Scope to this plant's active planting (optional)."
},
"bed": {
"type": "string",
"description": "Scope to this bed (optional; ignored if plant is given)."
},
"type": {
"type": "string",
"enum": [
"water",
"fertilize",
"custom"
],
"description": "Default water."
},
"everyDays": {
"type": "number",
"description": "Repeat every N days (1–365). Use this OR weekdays."
},
"weekdays": {
"type": "array",
"items": {
"type": "string"
},
"description": "Repeat on these weekdays, e.g. ['monday','thursday']. Use this OR everyDays."
},
"amount": {
"type": "string",
"description": "Optional, e.g. '2 L'."
},
"label": {
"type": "string",
"description": "Optional label (mainly for custom)."
},
"startDate": {
"type": "string",
"description": "First due date YYYY-MM-DD; default today."
},
"endsOn": {
"type": "string",
"description": "Optional last date YYYY-MM-DD (inclusive); no task after it. Use at most one of endsOn / endsAfter."
},
"endsAfter": {
"type": "number",
"description": "Optional: stop after this many completions. Use at most one of endsOn / endsAfter."
}
}
}🔴update_planting(garden, plant, plantingId, status, notes, ...)
Change a planting's status (active/finished/failed), notes, quantity, transplant date, variety, or MOVE it to another bed (pass bed with the target bed's name — history stays attached; any layout position is cleared, re-place with place_planting). Identify the planting by plant name or plantingId.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"plant": {
"type": "string",
"description": "Plant name of the planting to update."
},
"plantingId": {
"type": "string",
"description": "Or the planting id directly."
},
"status": {
"type": "string",
"enum": [
"active",
"finished",
"failed"
]
},
"notes": {
"type": "string"
},
"quantity": {
"type": "number"
},
"bed": {
"type": "string",
"description": "Move the planting to this bed (by name)."
},
"transplantedAt": {
"type": "string",
"description": "ISO date the seedling went into the bed."
},
"variety": {
"type": "string",
"description": "Variety/cultivar; stored on the plant."
}
}
}🔴delete_planting(garden, plant, plantingId)
Remove a planting from the garden. Siltwell archives it: it disappears from the app and from these tools, and its care schedules stop. Its harvests, events and photos stay stored, but the app has no way to restore it. Identify by plant name or plantingId. Use when the user says to delete/remove a planting (e.g. one added by mistake).
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"plant": {
"type": "string",
"description": "Plant name of the planting to remove."
},
"plantingId": {
"type": "string",
"description": "Or the planting id directly."
}
}
}🔴delete_bed(garden, bed)
Remove a bed from the garden. Siltwell archives it: it leaves the bed lists in the app and in these tools, its care schedules stop, and planned plantings queued for it are skipped. Past weather history still shows its name. The app has no way to restore it. Blocked while the bed has active plantings; remove or finish those first. Identify by bed name.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"bed": {
"type": "string",
"description": "The bed's name."
}
},
"required": [
"bed"
]
}🔴delete_schedule(garden, scheduleId, plant, bed, type)
Turn off a recurring care schedule (stops its reminders). Identify it by scheduleId, or by scope — plant (its active planting), bed, or garden-wide (neither) — optionally narrowed by type (water/fertilize/custom). Use when the user says to stop a watering/feeding reminder.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"scheduleId": {
"type": "string",
"description": "The schedule's id."
},
"plant": {
"type": "string",
"description": "Scope: this plant's active planting."
},
"bed": {
"type": "string",
"description": "Scope: this bed."
},
"type": {
"type": "string",
"enum": [
"water",
"fertilize",
"custom"
],
"description": "Narrow to this care type."
}
}
}🔴update_harvest(garden, plant, harvestId, quantity, unit, ...)
Correct a logged harvest — the most-recent harvest of a plant (by name) or a specific harvestId. Edit quantity, unit, notes, or the date. Use when the user says a harvest they recorded was wrong.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"plant": {
"type": "string",
"description": "Edit the most-recent harvest of this plant."
},
"harvestId": {
"type": "string",
"description": "Or a specific harvest id."
},
"quantity": {
"type": "number",
"description": "Corrected amount (> 0)."
},
"unit": {
"type": "string",
"enum": [
"g",
"kg",
"lb",
"oz",
"pcs"
],
"description": "lb and oz are stored as grams and need a quantity alongside."
},
"notes": {
"type": "string"
},
"harvestedAt": {
"type": "string",
"description": "Corrected ISO datetime."
}
}
}🔴place_planting(garden, plant, plantingId, xCm, yCm, ...)
Place or move a planting on its bed's layout grid — set its position (xCm, yCm measured from the bed's top-left corner) and footprint (wCm × hCm) in centimeters. Identify the planting by plant name or plantingId. Use when the user wants to arrange, position, or move a plant within its bed. For a planting that already spans several grid squares, use the app's layout editor instead.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"plant": {
"type": "string",
"description": "Plant name of the planting to place."
},
"plantingId": {
"type": "string",
"description": "Or the planting id directly."
},
"xCm": {
"type": "number",
"description": "X offset from the bed's top-left, in cm (≥ 0)."
},
"yCm": {
"type": "number",
"description": "Y offset from the bed's top-left, in cm (≥ 0)."
},
"wCm": {
"type": "number",
"description": "Footprint width in cm (> 0)."
},
"hCm": {
"type": "number",
"description": "Footprint height in cm (> 0)."
}
},
"required": [
"xCm",
"yCm",
"wCm",
"hCm"
]
}🟢list_planned_plantings(garden)
List the garden's succession plan — future plantings queued for a bed that haven't been sown yet (only status='planned'; done/skipped entries are omitted). Use when the user asks what's coming up next, what they've planned to plant, or wants to review their succession plan. For plantings already in the ground, use query_plantings instead.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
}
}
}🟡add_planned_planting(garden, bed, displayName, targetDate, method, ...)
Queue a future planting for a bed as part of a succession plan — it is NOT yet sown (use add_planting for something the user already planted). Use when the user wants to plan ahead, e.g. "plan to plant more carrots in Bed 2 on August 15".
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"bed": {
"type": "string",
"description": "The bed's name."
},
"displayName": {
"type": "string",
"description": "What to call this planting, e.g. 'Fall Carrots'."
},
"targetDate": {
"type": "string",
"description": "Planned planting date, YYYY-MM-DD."
},
"method": {
"type": "string",
"enum": [
"direct_seed",
"indoor_start",
"transplanted_seedling"
],
"description": "Default direct_seed."
},
"cropSlug": {
"type": "string",
"description": "Optional catalog crop slug."
},
"quantity": {
"type": "number"
},
"notes": {
"type": "string"
}
},
"required": [
"bed",
"displayName",
"targetDate"
]
}🔴update_planned_planting(garden, id, status, targetDate, quantity, ...)
Update a queued succession-plan entry: change its status (planned/done/skipped), reschedule its targetDate, or adjust quantity/notes. Identify it by id (from list_planned_plantings). Use when the user sows a planned planting (mark status done), decides to skip it, or wants to reschedule/adjust it.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"id": {
"type": "string",
"description": "The planned planting's id (from list_planned_plantings)."
},
"status": {
"type": "string",
"enum": [
"planned",
"done",
"skipped"
]
},
"targetDate": {
"type": "string",
"description": "New planned date, YYYY-MM-DD."
},
"quantity": {
"type": "number"
},
"notes": {
"type": "string"
}
},
"required": [
"id"
]
}🔴delete_planned_planting(garden, id)
Remove an entry from the succession plan outright (a queued future planting that hasn't been sown). This is a hard delete, not recoverable — for a planting already sown/growing, use delete_planting instead. Identify it by id (from list_planned_plantings).
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"id": {
"type": "string",
"description": "The planned planting's id (from list_planned_plantings)."
}
},
"required": [
"id"
]
}🟢get_season_plan(garden, today)
Compute the garden's rest-of-season planting schedule: every bed's next crops, chained forward to the effective first frost, deconflicted across beds with crop rotation and curated sow windows. Returns a PROPOSAL only — nothing is written; use add_planned_planting to accept a row into the succession plan. Returns every bed's chain, or one bed's full chain plus remainingCount for the rest when the garden's plan covers one bed.
Input Schema
{
"type": "object",
"properties": {
"garden": {
"type": "string",
"description": "Garden name; defaults to the user's first garden."
},
"today": {
"type": "string",
"description": "Optional YYYY-MM-DD to plan from; defaults to today in the garden's timezone."
}
}
}🟢lookup_frost_dates(place, latitude, longitude)
Average last spring frost, average first fall frost and hardiness zone for any place, from 10 years of weather records. Works without a Siltwell account. Dates are MM-DD. For the signed-in user's own garden, get_plan returns the garden's zone and frost dates, with the frost dates adjusted for its microclimate.
Input Schema
{
"type": "object",
"properties": {
"place": {
"type": "string",
"description": "Town plus region or country, for example \"Portland, Oregon\". Omit it to use the signed-in user's garden."
},
"latitude": {
"type": "number",
"description": "Latitude in decimal degrees. Give it with longitude instead of place."
},
"longitude": {
"type": "number",
"description": "Longitude in decimal degrees. Give it with latitude instead of place."
}
}
}🟢lookup_planting_windows(place, latitude, longitude, crops)
When to start seeds indoors, plant out, and sow for a fall harvest at any place, crop by crop, with the days left to sow today. Works without a Siltwell account. Dates are YYYY-MM-DD. Without crops, it returns the 30 crops with the soonest next step; pass crops to see others. For the signed-in user's own garden, get_plan returns sowing and transplant windows for the garden's own plants, counted from its microclimate-adjusted last frost date.
Input Schema
{
"type": "object",
"properties": {
"place": {
"type": "string",
"description": "Town plus region or country, for example \"Portland, Oregon\". Omit it to use the signed-in user's garden."
},
"latitude": {
"type": "number",
"description": "Latitude in decimal degrees. Give it with longitude instead of place."
},
"longitude": {
"type": "number",
"description": "Longitude in decimal degrees. Give it with latitude instead of place."
},
"crops": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 20,
"description": "Crop names to include, for example [\"tomato\", \"garlic\"]. Omit to get the 30 crops with the soonest next step."
}
}
}🟢lookup_growing_season(place, latitude, longitude)
Frost-free season length and seasonal growing degree days at any place, and whether heat-loving crops get enough heat to ripen. Works without a Siltwell account. For the signed-in user's own garden, get_plan returns the microclimate-adjusted frost dates that bound its season, and get_history returns its daily growing degree days.
Input Schema
{
"type": "object",
"properties": {
"place": {
"type": "string",
"description": "Town plus region or country, for example \"Portland, Oregon\". Omit it to use the signed-in user's garden."
},
"latitude": {
"type": "number",
"description": "Latitude in decimal degrees. Give it with longitude instead of place."
},
"longitude": {
"type": "number",
"description": "Longitude in decimal degrees. Give it with latitude instead of place."
}
}
}🟢lookup_frost_risk(place, latitude, longitude)
Forecast lows for the next 7 days at any place and the nights at risk of frost. Each frost night is dated by the morning its low falls on, so protect plants the evening before that date. Works without a Siltwell account. For the signed-in user's own garden, get_forecast returns this forecast with the garden's microclimate adjustment applied.
Input Schema
{
"type": "object",
"properties": {
"place": {
"type": "string",
"description": "Town plus region or country, for example \"Portland, Oregon\". Omit it to use the signed-in user's garden."
},
"latitude": {
"type": "number",
"description": "Latitude in decimal degrees. Give it with longitude instead of place."
},
"longitude": {
"type": "number",
"description": "Longitude in decimal degrees. Give it with latitude instead of place."
}
}
}Community
Evidence