Skip to main content
Glama
tresor4k

macalc

calculate_fertilizer_npk

Calculate the precise NPK fertilizer amount needed for your lawn, vegetables, fruit trees, flowers, or potatoes by providing surface area, crop type, and soil type (clay, sandy, loam, chalky). Get the total kilograms of fertilizer required.

Instructions

Calculate NPK fertilizer quantities needed based on crop type and soil type. Returns: {total_kg}. See list_bundles for related 'jardinage' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
surface_m2YesSurface area in square meters
crop_typeYesType of crop to fertilize
soil_typeYesType of soil

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Returns: {total_kg}', omitting details like calculation assumptions, units, or side effects.

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 purpose and a reference to related tools. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description adequately covers basic purpose but lacks details about NPK ratio assumptions or application context. Output schema exists but not shown, and description references it minimally.

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 has 100% description coverage for parameters, so baseline is 3. The description adds minimal extra meaning beyond the schema, just indicating return value 'total_kg'.

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?

Description specifies verb 'calculate', resource 'NPK fertilizer quantities', and mentions 'based on crop type and soil type'. It also references related 'jardinage' calculators via list_bundles, distinguishing it from siblings.

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?

Description provides a hint by referencing list_bundles for related calculators, but lacks explicit guidance on when to use this tool vs alternatives or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server