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

ALOC Model Context Protocol (MCP) Server

Official
by MaSSTeck

aloc_get_platform_overview

Fetch ALOC assessment infrastructure details—supported African exam bodies, subjects, year coverage (1988–2026), and API layers—to plan integrations.

Instructions

Discover ALOC assessment infrastructure overview, supported African exam bodies (WAEC, JAMB, NECO, Post-UTME), subject list, year coverage (1988–2026), and API layers. Free (0 credits).

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_platform_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.13

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 behavioral burden, and it does add one genuinely useful trait: the call is free (0 credits), which an agent needs when budgeting. However, it says nothing about the shape of the response, whether the data is static or live, or whether the listed subjects/years are exhaustive or a summary.

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?

It is a single front-loaded sentence with the verb and resource first and the content list after, plus the cost note at the end. The enumeration is long but each item conveys distinct payload content, so little is wasted.

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 no-parameter, no-output-schema overview tool, the description compensates for the missing output schema by listing what the overview contains (bodies, subjects, years, API layers). The only gap is that it does not say how an agent should use the result to route to the more specific sibling tools.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the schema is fully covered by definition. The description correctly avoids inventing input details; baseline 4 applies.

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 leads with a specific verb ('Discover') and names the resource ('ALOC assessment infrastructure overview'), then enumerates its contents: exam bodies, subject list, year coverage, and API layers. That enumeration distinguishes it from neighbors like aloc_get_coverage_matrix or aloc_get_sitemap, though it never names those siblings explicitly to confirm the boundary.

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?

An orientation use case is strongly implied by 'Discover ... overview' and the zero-parameter schema, but the description never states when to call this versus aloc_get_coverage_matrix, aloc_get_sitemap, or aloc_get_curriculum_taxonomy. The agent must infer that this is the entry-point tool.

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