Skip to main content
Glama
tresor4k

macalc

calculate_seed_quantity

Determine the number of seeds required by entering surface area, row and plant spacing, and optional germination rate.

Instructions

Calculate the number of seeds needed based on surface area, spacing and germination rate. See list_bundles for related 'jardinage' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
surface_m2YesSurface area in square meters
row_spacing_cmYesDistance between rows in centimeters
plant_spacing_cmYesDistance between plants in a row in centimeters
germination_rate_pctNoGermination rate in percent (default 85%)

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.
Behavior3/5

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

No annotations exist, so description carries full burden. It implies a read-only, deterministic calculation without side effects, but does not explicitly state these traits. For a simple calculator, this is acceptable but not exceptional.

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 concise sentences: first states purpose with key inputs, second provides pointer to related tools. No wasted words, front-loaded with essential information.

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?

With full schema coverage and an output schema, the description is mostly complete for a calculation tool. It could mention output type or formula, but the pointer to list_bundles adds helpful context.

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?

Schema descriptions cover all 4 parameters with types, units, and constraints (100% coverage). The description groups them but adds no new semantic meaning beyond the schema.

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?

Clearly states the tool's purpose: calculating seed quantity from surface area, spacing, and germination rate. It is distinct among many calculate_* siblings due to specific gardening domain reference and pointer to list_bundles for related calculators.

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

Usage Guidelines4/5

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

Describes when to use (seed quantity calculation based on specified inputs) and directs to list_bundles for related tools. Lacks explicit exclusion criteria or direct comparisons but is adequate for a focused calculator.

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