Skip to main content
Glama

estimate_study_costs

Estimate and compare the total annual cost of studying in one or more countries for an African postgraduate student. Covers 32 destinations: Tier 3 affordable EU (Germany, France, Italy, Austria, Portugal, Poland, Czech Republic, Estonia, Baltic states, Balkans), Tier 2 full-tuition scholarship countries (Netherlands, Belgium, Scandinavian countries, Japan, South Korea, Switzerland), and benchmark high-cost countries (UK, USA, Canada, Australia). Returns annual cost breakdown: tuition, living, flights, health insurance, visa fee, and total. Use scholarship_mode=true to show the self-funding gap when tuition is already covered by a scholarship.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lifestyleNoBudget = shared accommodation, public transport, cooking at home. Comfortable = private room, occasional dining out. Default: budget.
degree_levelNoDegree level. Default: masters.
destinationsNoList of country IDs or names to compare. IDs: germany, france, italy, austria, portugal, poland, czech_republic, estonia, latvia, lithuania, romania, slovakia, croatia, hungary, slovenia, bulgaria, greece, netherlands, belgium, ireland, denmark, finland, sweden, norway, switzerland, japan, south_korea, hong_kong, uk, usa, canada, australia. Alternatively use common names: 'Germany', 'UK', 'United States', etc. Provide one to three destinations.
scholarship_modeNoIf true, sets tuition to €0 (assuming tuition is covered by scholarship) and shows only living costs, flights, insurance, and visa. Useful for comparing cities when a student already has a tuition scholarship. Default: false.

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses the principal behavior by listing the returned cost components and explains the effect of scholarship_mode on the output. For a read-only estimation tool, this is strong transparency, though it could ideally mention data sources or assumptions.

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?

The description is two dense sentences with the purpose front-loaded and no filler. The destination tier list is useful though partially redundant with the schema's enum names. Overall, it is concise and well-structured.

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?

Since there is no output schema, the description correctly lists the return fields (tuition, living, flights, health insurance, visa fee, total). It also covers the target audience, destination scope, and scholarship_mode. A minor gap is the lack of details about data sources or currency, but the description is sufficient for a 4-parameter tool with full schema coverage.

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% and each parameter already has a detailed description. The main description adds marginal value by grouping destinations into tiers and clarifying that scholarship_mode reveals the self-funding gap, but the schema already covers the behavioral details. Thus, baseline 3 is appropriate.

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 opens with a specific verb phrase 'Estimate and compare the total annual cost of studying' and clearly defines the target audience ('African postgraduate student') and scope ('one or more countries'). This clearly differentiates it from sibling tools like search_scholarships or check_visa, which focus on different aspects of study planning.

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?

The description provides clear context for when the tool is useful, such as comparing countries or using scholarship_mode=true to show the self-funding gap. It does not explicitly contrast with alternatives, but the sibling tools' purposes (visa, GPA, scholarships) make the cost-estimation use case unambiguous; lacking explicit 'when not to use' guidance prevents a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool serves a distinct function: visa checks, GPA conversion, cost estimation, scholarship lookup (specific), matching, and searching. There is clear separation between search and get/match, and between cost, visa, and GPA utilities.

Naming Consistency5/5

All tools use a clear verb_noun pattern: check_visa, convert_gpa, estimate_study_costs, get_scholarship, match_scholarships, search_scholarships. The verbs accurately describe the action, and nouns are the domain objects. Perfect consistency.

Tool Count5/5

Six tools is an ideal size for a specialized education/scholarship assistant. Each tool covers a core need without redundancy, and the count is well within the sweet spot for agent usability.

Completeness4/5

The toolset covers the core pre-application workflow: checking visa feasibility, converting GPA, estimating costs, and finding/matching scholarships. The main gap is lack of direct scholarship application or document submission tools, but those are likely outside the server's scope (it's a research/planning assistant).

Resources