Skip to main content
Glama

KCSE mean grade and KUCCPS minimums

kenya.kcse_mean_grade
Read-only

Use this when a student in Kenya gives their KCSE subject grades and asks for their mean grade, total points, or whether they reach the minimum for a degree, diploma or certificate through KUCCPS. It counts Mathematics, the better of English and Kiswahili, and the five strongest others, as KNEC's regulations state. Do not use it for a programme's cluster points or cut-off, for grades from another examination, or to answer exam questions.

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": {
      "mathematics": "<mathematics>",
      "english": "<english>",
      "kiswahili": "<kiswahili>",
      "other_subjects": "<other_subjects>"
    },
    "name": "kenya.kcse_mean_grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
englishYesGrade in English.
kiswahiliYesGrade in Kiswahili (or Kenyan Sign Language).
mathematicsYesGrade in Mathematics.
other_subjectsYesThe grades in the other subjects, separated by commas, for example "B+, A-, C+, B, C". At least four.

Output Schema

NameRequiredDescriptionDefault
examYes
noteYes
read_onYes
sourcesYes
mean_gradeYes
explore_urlNo
how_countedYes
total_pointsYes
subjects_countedYes
placement_minimumsNo
reaches_minimum_forYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/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 fully covered by structured fields. The description's real added value is disclosing the KNEC computation rule (Mathematics, better of English/Kiswahili, five strongest others), but it does not explain how grades map to points or what the numeric outputs look like — partly excused by the presence of an output schema.

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?

Three sentences, front-loaded with the use case, then the computation rule, then exclusions. No filler, and each sentence adds distinct information an agent needs.

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 read-only computation tool with full schema coverage, annotations, and an output schema, the description covers trigger, method, and exclusions well. It is only slightly short of complete in not clarifying the source or vintage of the KUCCPS minimums it compares against.

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 parameter documentation is already handled and the baseline would be 3. The description goes beyond it by explaining the computation rule, which clarifies why both english and kiswahili are required (the better of the two counts) and why other_subjects needs at least five entries — meaningful semantics the schema alone does not convey.

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?

States a specific verb and resource — computing KCSE mean grade, total points, and KUCCPS minimum eligibility — and scopes it to a Kenyan student's KCSE grades. An agent can immediately distinguish it from siblings like ghana.bece_aggregate or grades.scale because the exam system and outputs are named explicitly.

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?

Gives a clear trigger (student supplies KCSE subject grades and asks for mean grade, points, or KUCCPS eligibility) plus three explicit exclusions: cluster points/cut-offs, non-KCSE examinations, and exam-question answering. It does not name a specific sibling tool to redirect to for those cases, which is the only gap.

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