Skip to main content
Glama
tresor4k

macalc

calculate_puissance_fiscale

Calculate French fiscal horsepower (CV) using CO2 g/km and engine power in kW. Returns raw CV and rounded fiscal CV for vehicle tax assessment.

Instructions

French fiscal horsepower CV = (CO2/45) + (P_kW/40)^1.6. Returns: {cv_raw, cv_fiscaux}. See list_bundles for related 'auto-transport' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
co2_g_kmYesCO2 g/km
power_kwYesEngine power in kW

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.
Behavior4/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 discloses the exact formula and output fields, offering transparent behavior. However, it does not discuss edge cases, authorization, 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 concise, front-loaded sentences. No wasted words; the formula and output are immediately communicated, and the sibling reference is succinct.

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?

Simple calculator with 2 params and an output schema. The description covers the formula and return fields adequately. The sibling reference adds completeness for context.

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?

Schema coverage is 100%, baseline 3. The description adds value by showing how parameters (co2_g_km, power_kw) are used in the formula, providing semantic meaning beyond the schema descriptions.

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 it calculates French fiscal horsepower using a specific formula (CO2/45 + (P_kW/40)^1.6) and provides the return structure. The sibling reference distinguishes it from 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 Guidelines3/5

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

The description mentions list_bundles for related calculators but does not explicitly state when to use this tool vs. alternatives or provide exclusions. Usage is implied but not fully guided.

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