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

ALOC Model Context Protocol (MCP) Server

Official
by MaSSTeck

aloc_get_subject_years

Retrieve available examination years for a subject, optionally filtered by exam body such as WAEC, JAMB, or NECO. Confirm which years have questions before planning study or assessment sessions.

Instructions

List all available examination years for a specific subject and exam body. Free (0 credits).

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": {
      "subject": "<subject>"
    },
    "name": "aloc_get_subject_years"
  }
}

Input Schema

NameRequiredDescriptionDefault
subjectYesSubject name (e.g. 'mathematics', 'physics', 'english')
examTypeNoOptional examination body filter

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 supplied, the description does disclose one valuable behavioral trait: the call is free at 0 credits, which matters for cost-aware planning. It does not state whether the result is a flat list, what happens when a subject/exam-body combination has no years, or whether the list is ordered, leaving meaningful behavioral gaps for an annotation-free tool.

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 short sentences, zero filler, with the core purpose front-loaded and the cost disclosure second. Nothing could be removed without losing information.

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 simple two-parameter read-only lookup with no output schema, the definition covers what the tool returns conceptually (available years) and its cost profile. The omission of return ordering or empty-result behavior is minor at this complexity level.

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 both 'subject' and 'examType' are already documented including the enum values. The description restates the same two concepts ('specific subject and exam body') without adding format, casing, or fallback guidance, so the baseline of 3 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 uses a specific verb and resource ('List all available examination years') and scopes it to a subject and exam body, which distinguishes it from siblings like aloc_get_coverage_matrix or aloc_get_curriculum_taxonomy. It does not explicitly name an alternative, but the resource is concrete enough that an agent knows what it retrieves.

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 the wording ('for a specific subject and exam body') and the cost note gives a practical reason to prefer it over paid siblings when only year availability is needed. However, there is no explicit statement of when to use this versus looking up questions or coverage data, and no prerequisites or exclusions are given.

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