Skip to main content
Glama

Calculate match score

calculate_match_score

Given a user's GPA and test score, calculate match category (Safety/Target/Reach/Far Reach), admission probability, and percentiles for one school or a ranked list. Public — no authentication required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "program": "<program>"
    },
    "name": "calculate_match_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpaNoCumulative GPA on a 4.0 scale (omit for ATAR-based Australian schools)
atarNoAustralian Tertiary Admission Rank (0-99.95). Used instead of test_score/gpa for Australian schools, which select on a published ATAR cutoff.
limitNoNumber of top schools to return when no school_slug given
programYesProgram type
test_scoreNoTest score: LSAT 120-180, MCAT 472-528, DAT 200-600 (the scale since March 2025; the retired 1-30 scale is also accepted), OAT 200-400, GMAT/GRE for MBA. Omit for pharmacy (PCAT retired 2024 — GPA-only) and for ATAR-based Australian schools.
school_slugNoIf provided, calculate for this school only. Otherwise returns a ranked list.
work_experience_yearsNoYears of full-time work experience (MBA programs only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / test_score / description
      Previous value: -"Test score: LSAT 120-180, MCAT 472-528, DAT 1-30, OAT 200-400, GMAT/GRE for MBA. Omit for pharmacy (PCAT retired 2024 — GPA-only) and for ATAR-based Australian schools."New value: +"Test score: LSAT 120-180, MCAT 472-528, DAT 200-600 (the scale since March 2025; the retired 1-30 scale is also accepted), OAT 200-400, GMAT/GRE for MBA. Omit for pharmacy (PCAT retired 2024 — GPA-only) and for ATAR-based Australian schools."
  2. Changed1 schema field changed
    • changedInput schema / properties / test_score / description
      Previous value: -"Test score: LSAT 120-180, MCAT 472-528, DAT 1-30, OAT 200-400, GMAT/GRE for MBA, PCAT for pharmacy. Omit for ATAR-based Australian schools."New value: +"Test score: LSAT 120-180, MCAT 472-528, DAT 1-30, OAT 200-400, GMAT/GRE for MBA. Omit for pharmacy (PCAT retired 2024 — GPA-only) and for ATAR-based Australian schools."
  3. Changed4 schema fields changed
    • addedInput schema / properties / atar
      Added value: +{
      +  "description": "Australian Tertiary Admission Rank (0-99.95). Used instead of test_score/gpa for Australian schools, which select on a published ATAR cutoff.",
      +  "maximum": 99.95,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • changedInput schema / properties / gpa / description
      Previous value: -"Cumulative GPA on a 4.0 scale"New value: +"Cumulative GPA on a 4.0 scale (omit for ATAR-based Australian schools)"
    • changedInput schema / properties / test_score / description
      Previous value: -"Test score: LSAT 120-180, MCAT 472-528, DAT 1-30, OAT 200-400, GMAT/GRE for MBA, PCAT for pharmacy"New value: +"Test score: LSAT 120-180, MCAT 472-528, DAT 1-30, OAT 200-400, GMAT/GRE for MBA, PCAT for pharmacy. Omit for ATAR-based Australian schools."
    • changedInput schema / required
      Previous value: -[
      -  "program",
      -  "gpa",
      -  "test_score"
      -]New value: +[
      +  "program"
      +]
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the tool is public and requires no authentication, and it describes the outputs (match category, probability, percentiles). However, it does not explain determinism, idempotency, error behavior for invalid inputs, or ranking criteria, leaving meaningful behavioral gaps.

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 with zero waste. The core calculation and its outputs are front-loaded, followed by the important scope and authentication note.

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?

For a seven-parameter calculation tool with no output schema, the description adequately covers the main return values and the single-school-versus-ranked-list behavior. It could be richer about what percentiles represent and how results are ordered, but the essentials for calling the tool correctly are present.

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 description coverage is 100%, so all seven parameters are already documented. The description adds only the high-level mapping of 'one school or a ranked list' to school_slug/limit and does not clarify the GPA-vs-ATAR tradeoff, program-specific test scales, or work experience, which the schema covers instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('calculate match category, admission probability, and percentiles') and states the scope ('for one school or a ranked list'). It is clear about what the tool produces, but it does not explicitly contrast itself with siblings like get_school_stats or search_schools.

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?

Usage is implied by 'Given a user's GPA and test score' and 'for one school or a ranked list,' but there is no explicit guidance on when to choose this tool over get_school_stats or search_schools, nor any stated exclusions or prerequisites beyond the authentication note.

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.

Resources