Atlarium Habitat Database MCP

Generate fertilization plan

generate_fertilization_plan

Read-onlyIdempotent

Generate an advisory non-persistent fertilization plan from public Atlarium catalog data.

Input Schema

TableJSON Schema

Name	Required	Description
`items`	No	Optional supplied fertilization plan items to analyze.
`regime`	No	Optional fertilization regime name or strategy.
`targets`	No	Optional target nutrient concentrations.
`language`	No	Optional preferred response language: it, en or es.
`measurements`	No	Optional current measurements for nutrient-gap calculations.
`volume_liters`	Yes	Tank or habitat volume in liters.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`tool`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 2, 2026

removedOutput schema / properties / generated_at
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / required

Previous value: -[
-  "data",
-  "generated_at",
-  "tool"
-]New value: +[
+  "data",
+  "tool"
+]

Changed41 schema fields changedJun 20, 2026

addedInput schema / properties / items / description

Added value: +"Optional supplied fertilization plan items to analyze."

addedInput schema / properties / items / items / properties / brand_name / description
```
Added value: +"Optional fertilizer brand name for this dosing item."
```
addedInput schema / properties / items / items / properties / days_of_week / description
```
Added value: +"Scheduled dosing days as numbers from 1 to 7."
```
addedInput schema / properties / items / items / properties / days_of_week / items / description
```
Added value: +"Day of week number from 1 to 7."
```
addedInput schema / properties / items / items / properties / dose_unit / description
```
Added value: +"Dose unit, defaulting to ml."
```
addedInput schema / properties / items / items / properties / dose_value / description
```
Added value: +"Dose amount per scheduled application."
```
addedInput schema / properties / items / items / properties / method / description
```
Added value: +"Dosing method for the fertilizer item."
```
addedInput schema / properties / items / items / properties / notes / description
```
Added value: +"Optional non-persistent notes for this dosing item."
```
addedInput schema / properties / items / items / properties / product_name / description
```
Added value: +"Fertilizer product name for this dosing item."
```
addedInput schema / properties / items / items / properties / sort_order / description
```
Added value: +"Optional sort order for displaying plan items."
```

addedInput schema / properties / language / description

Added value: +"Optional preferred response language: it, en or es."

addedInput schema / properties / measurements / description

Added value: +"Optional current measurements for nutrient-gap calculations."

addedInput schema / properties / measurements / items / properties / kind / description
```
Added value: +"Measured nutrient or water parameter name."
```
addedInput schema / properties / measurements / items / properties / measured_at / description
```
Added value: +"Optional ISO datetime for when the measurement was taken."
```

changedInput schema / properties / measurements / items / properties / value / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / measurements / items / properties / value / description
```
Added value: +"Measured numeric value; omit or use null when unknown."
```

addedInput schema / properties / regime / description

Added value: +"Optional fertilization regime name or strategy."

addedInput schema / properties / targets / description

Added value: +"Optional target nutrient concentrations."

changedInput schema / properties / targets / properties / boron_mg_l / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / targets / properties / boron_mg_l / description
```
Added value: +"Target boron concentration in mg/L."
```

changedInput schema / properties / targets / properties / calcium_mg_l / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / targets / properties / calcium_mg_l / description
```
Added value: +"Target calcium concentration in mg/L."
```

changedInput schema / properties / targets / properties / copper_mg_l / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / targets / properties / copper_mg_l / description
```
Added value: +"Target copper concentration in mg/L."
```

changedInput schema / properties / targets / properties / iron_mg_l / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / targets / properties / iron_mg_l / description
```
Added value: +"Target iron concentration in mg/L."
```

changedInput schema / properties / targets / properties / magnesium_mg_l / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / targets / properties / magnesium_mg_l / description
```
Added value: +"Target magnesium concentration in mg/L."
```

changedInput schema / properties / targets / properties / manganese_mg_l / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / targets / properties / manganese_mg_l / description
```
Added value: +"Target manganese concentration in mg/L."
```

changedInput schema / properties / targets / properties / molybdenum_mg_l / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / targets / properties / molybdenum_mg_l / description
```
Added value: +"Target molybdenum concentration in mg/L."
```

changedInput schema / properties / targets / properties / nitrogen_mg_l / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / targets / properties / nitrogen_mg_l / description
```
Added value: +"Target nitrogen concentration in mg/L."
```

changedInput schema / properties / targets / properties / phosphorus_mg_l / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / targets / properties / phosphorus_mg_l / description
```
Added value: +"Target phosphorus concentration in mg/L."
```

changedInput schema / properties / targets / properties / potassium_mg_l / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / targets / properties / potassium_mg_l / description
```
Added value: +"Target potassium concentration in mg/L."
```

changedInput schema / properties / targets / properties / zinc_mg_l / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Finite numeric value for advisory calculations.",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / targets / properties / zinc_mg_l / description
```
Added value: +"Target zinc concentration in mg/L."
```
addedInput schema / properties / volume_liters / description
```
Added value: +"Tank or habitat volume in liters."
```

AddedJun 20, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds 'non-persistent' and 'advisory', which clarifies that no stored changes occur and the output is consultative. This supplements the annotation without contradiction, though more detail on data validation or error behavior would be welcome.

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?

The description is a single, dense sentence that packs the core purpose ('generate'), scope ('advisory non-persistent'), and data source ('public Atlarium catalog') without any wasted words. Every term contributes to understanding the tool's behavior.

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?

Given the high complexity (nested objects, 6 params, output schema present), the description successfully conveys the essential function and safety profile. The output schema presumably documents return values, so the description need not repeat those, but a brief note on when to provide items vs targets vs measurements would improve completeness.

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?

Input schema covers all 6 parameters with 100% description coverage, so the baseline of 3 applies. The description adds minimal parameter-specific meaning beyond stating the data source (public Atlarium catalog), which hints that product_name and brand_name should reference catalog entries but does not explain parameter interactions like how targets and measurements are used.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates an advisory, non-persistent fertilization plan using public Atlarium catalog data. This distinguishes it from sibling tools like calculate_fertilizer_dose (single dose) and get_fertilization_regime (retrieve existing), making the purpose specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives. Sibling tools such as calculate_nutrient_gaps or calculate_weekly_dose_totals serve related purposes, but no differentiation or exclusion criteria are mentioned, leaving the selection decision to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Atlarium Habitat Database MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.