Skip to main content
Glama
tresor4k

macalc

calculate_travel_budget

Plan your trip budget by estimating costs for transport, accommodation, food, and activities. Get total and per-day breakdown based on destination, duration, and number of travelers.

Instructions

Estimate total trip budget by category (transport, accommodation, food, activities). Use for trip planning. Inputs: destination, days, traveler count, comfort level. Returns total and per-day breakdown. See list_bundles for related 'voyage' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destinationYesDestination region
daysYesNumber of travel days
travelersYesNumber of travelers

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 are provided, so the description carries full burden. It describes estimation and return format but does not disclose side effects, safety, or rate limits, which is adequate for a simple calculator.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences front-load purpose, usage, inputs, and outputs. It is concise but includes an erroneous parameter reference.

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?

Despite having an output schema, the description explains returns adequately. However, the mention of a non-existent parameter and lack of sibling differentiation limit completeness.

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

Parameters1/5

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

The description mentions 'comfort level' as an input, but the schema has no such parameter. This adds confusion and contradict schema, reducing value.

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 estimates a trip budget by category, with specific inputs and outputs, distinguishing it from sibling calculation tools.

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?

It says 'Use for trip planning' and directs to 'list_bundles for related calculators', providing clear context but no explicit exclusions.

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