Skip to main content
Glama

JAMB minimum UTME score and O'level credits

nigeria.admission_minimums
Read-only

Use this when a candidate in Nigeria gives a UTME score, O'level (WAEC or NECO) grades, or both, and asks whether they reach JAMB's national minimum for a university, polytechnic or college, or whether they have the O'level credits needed. Do not use it to give a university's or programme's own cut-off or post-UTME score, for another country's examinations, or to answer exam questions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nigeria.admission_minimums"
  }
}

Input Schema

NameRequiredDescriptionDefault
englishNoO'level grade in English Language. Leave out if only a UTME score is being checked.
utme_scoreNoThe UTME score. Leave out if only O'level grades are being checked.
institutionNoThe kind of institution. Leave out for university.
mathematicsNoO'level grade in Mathematics.
other_gradesNoO'level grades in the other subjects, with or without names, for example "Biology B3, Chemistry C5, Physics C6".
admission_yearNoThe year of admission. Leave out for 2026.

Output Schema

NameRequiredDescriptionDefault
noteYes
utmeNo
olevelNo
read_onYes
sourcesYes
explore_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the answer is authoritative only for JAMB's national floor, not an institution's own cut-off or post-UTME threshold, which sets caller expectations about the result's limits. It stops short of stating anything about determinism or year-dependence beyond the admission_year enum, so it is strong but not exhaustive.

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, both earning their place: the first front-loads the positive trigger and the second front-loads the exclusions. No filler, no restatement of the tool name, and the longest clause (the institution types) is necessary to bound the answer.

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?

With an output schema present and 100% parameter coverage, the description needs only to establish purpose and boundaries, which it does completely for a read-only lookup with six optional parameters. An agent could decide whether to call this and populate the arguments correctly from what is given.

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%, including per-parameter guidance such as leaving out english or utme_score when only one type of check is requested, and defaulting institution to university. The description restates the UTME/O'level inputs but adds no meaning about enumerations (institution kinds, admission_year) or the other_grades free-text format. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names the specific resource (JAMB's national minimum UTME score and O'level credit requirement) and the exact inputs that trigger it (UTME score, WAEC/NECO grades, or both). It also scopes the answer to national minimums for university, polytechnic or college, which distinguishes it from the Ghana/Kenya/South Africa siblings without needing their names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit trigger (candidate supplies UTME score and/or O'level grades and asks about reaching the national minimum) and explicit exclusions: institutional/programme cut-offs, post-UTME scores, other countries' examinations, and answering exam questions. This is the when/when-not/alternative pattern at full strength.

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