Skip to main content
Glama
ALOC Model Context Protocol (MCP) Server

ALOC Model Context Protocol (MCP) Server

Official
by MaSSTeck

aloc_get_curriculum_taxonomy

Fetch official WAEC, JAMB, or NECO curriculum structures with subject breakdowns and topic hierarchies to align study content and assessments with exam requirements.

Instructions

Retrieve official African examination curriculum structure, subject breakdown, and topic hierarchy.

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": "aloc_get_curriculum_taxonomy"
  }
}

Input Schema

NameRequiredDescriptionDefault
subjectNoSubject name
examTypeNoExamination body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.13

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read but never states that it is non-mutating, whether both parameters are optional filters, what is returned when they are omitted (full taxonomy versus empty), or how large the hierarchy response may be.

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?

A single front-loaded sentence with no filler; the resource is described before any qualifiers. It is efficient, though the trailing noun list (structure, breakdown, hierarchy) is somewhat redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (two optional enum/string filters, no nested objects), but with no output schema the description should say something about the shape or scale of the returned hierarchy, and it does not. Adequate to identify the tool, insufficient to predict its behavior on an unfiltered call.

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% and the examType enum (waec/jamb/neco) is fully enumerated in the schema, so the baseline is 3. The one semantic point the schema cannot convey — that both parameters are optional filters and what omitting them yields — is left unexplained by the description.

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 opens with a specific verb ("Retrieve") and names the concrete resource: official African examination curriculum structure, subject breakdown, and topic hierarchy. That is enough to distinguish it from data tools like aloc_search_questions or aloc_get_question_explanation, though it never explicitly contrasts itself with a sibling such as aloc_get_subject_years.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no named alternative. An agent must infer from the noun list alone that this is the reference-data lookup for curriculum hierarchy rather than an assessment or search tool.

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