Skip to main content
Glama
tresor4k

macalc

calculate_ects_credits

Calculate ECTS credits from study hours per week and weeks. Estimate total workload and balance against credit targets for European university course planning.

Instructions

Estimate ECTS credit workload (1 ECTS ≈ 25-30 study hours). Use for university course planning across Europe. Inputs: course hours, credits target. Returns expected workload and balance. See list_bundles for related 'education' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hours_per_weekYesStudy hours per week
weeksYesNumber of weeks
hours_per_creditNoHours per ECTS credit (standard: 25-30)

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?

Without annotations, description carries full burden. It describes returns ('expected workload and balance') and conversion factor but does not explicitly confirm read-only or non-destructive nature. Lacks explicit safety declaration.

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 plus a reference, front-loading purpose. No wasted words.

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?

Describes outputs and inputs adequately for a simple calculator. Could elaborate on return structure, but given the complexity, it is sufficient.

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%, so baseline is 3. Description adds value by summarizing inputs ('course hours, credits target') and contextualizing the default hours_per_credit with the 25-30 hour range.

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 clearly states specific verb 'Estimate' and resource 'ECTS credit workload' for university course planning in Europe. It distinguishes from sibling calculators by mentioning related 'education' 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?

Provides explicit usage context ('university course planning across Europe') and hints at alternatives via list_bundles. However, does not explicitly state when not to use or list direct alternatives.

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