Skip to main content
Glama
tresor4k

macalc

calculate_lawn_seed

Compute grass seed quantity in kilograms for a lawn by inputting area in square meters and seeding rate in grams per square meter. Useful for landscaping.

Instructions

Compute grass seed quantity (kg) for a lawn area at recommended seeding rate. Use for landscaping. Inputs: area m², seed rate g/m². Returns seed kg. See list_bundles for related 'construction' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
area_m2YesLawn area m²
rate_g_m2NoSeeding rate g/m²

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 provided, so description must fully disclose behavior. It describes inputs and output (seed kg) but lacks details on rounding, precision, or any computational assumptions beyond the recommended seeding rate.

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 sentences that are front-loaded with the core purpose, followed by usage hint and reference to related calculators. Every sentence is useful and concise.

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 tool's simplicity and the presence of an output schema, the description covers the essential aspects. It also provides context on related calculators. However, it could briefly mention the output unit (kg) which is already implied.

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 coverage is 100%, so the parameters are already well-documented. The description adds minimal extra meaning by noting 'recommended seeding rate' and default value, but does not significantly enhance understanding 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 it computes grass seed quantity in kg for a lawn area, with specific verb and resource. Distinguishes from siblings by mentioning 'Use for landscaping' and pointing to construction calculators via list_bundles.

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?

Explicitly says 'Use for landscaping' and references list_bundles for construction calculators, providing context for when to use this tool vs alternatives. However, it does not explicitly state 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