Skip to main content
Glama
tresor4k

macalc

calculate_grocery_unit_comparison

Compare unit prices of grocery items by normalizing quantities to standard units (kg, L). Identifies the best value and savings versus the priciest option.

Instructions

Compare unit prices of grocery items — normalizes g→kg, mL/cL→L. Returns: {best_value, savings_vs_priciest}. See list_bundles for related 'vie-quotidienne' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesItems: name, price, quantity, unit (kg/g/L/mL/cl/unit)

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; description covers normalization of units and return fields. However, it does not disclose potential error scenarios or whether the tool is read-only. Still, the essential behavior is described.

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, no extraneous information. Front-loads the primary action and returns.

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

Completeness5/5

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

Given the presence of output schema and full schema coverage, the description adds normalization details and a pointer to related tools. Fills necessary gaps for a grocery comparison tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers 100% of parameters; description reinforces normalization behavior for unit conversion, adding meaning beyond schema by explaining how units are standardized.

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 explicitly states 'Compare unit prices of grocery items' with normalization details and return structure. Clearly distinguishes from other calculation tools by focusing on grocery unit comparison.

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?

Description gives usage context: when needing to compare unit prices. Mentions related 'list_bundles' for 'vie-quotidienne' calculators, but does not explicitly exclude other use cases. No specific when-not-to-use guidance.

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