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

ALOC Model Context Protocol (MCP) Server

Official
by MaSSTeck

aloc_search_questions

Search curriculum-aligned WAEC, JAMB, and NECO exam questions by subject, year, topic, or difficulty to build targeted practice sets and assessments.

Instructions

Search and retrieve curriculum-aligned examination questions (WAEC, JAMB, NECO) with options, metadata, and difficulty levels. Consumes 1-3 ALOC 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_search_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoExamination year (e.g. 2022)
limitNoNumber of questions to return (max 15, default 5)
topicNoTopic filter (e.g. 'algebra', 'calculus', 'photosynthesis')
subjectYesSubject name (e.g. 'mathematics', 'english', 'biology', 'physics', 'chemistry', 'economics')
examTypeNoTarget African examination body
difficultyNoDifficulty score 1–5 (1=easy, 5=very hard) or alias ('easy', 'medium', 'hard')
contentSourceNoContent provenance filter. Defaults to historical past questions; pass synthetic or all to explicitly include AI-generated questions.historical
excludePassagesNoExclude reading-passage comprehension items

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.13

TDQS

B3.2/5.0
Behavior3/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. Disclosing that calls consume 1-3 ALOC credits is a genuinely useful, non-obvious behavioral fact that the schema does not convey, but it never explains what drives the cost from 1 to 3, nor does it cover auth needs, error behavior, or pagination.

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?

Two tight sentences with the resource scope front-loaded and the cost note placed where it will be read. No filler; the only thing missing is routing information, not economy of words.

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?

With 8 parameters, no annotations, and no output schema, the description should say more about the return shape than 'options, metadata, and difficulty levels'. It gives a hint of response content and the credit cost, but leaves the agent guessing about result structure and cost variability.

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%, with per-parameter descriptions including examples, defaults, enum values, and the difficulty alias mapping, so the schema already does the heavy lifting. The description adds no parameter-level meaning beyond naming the returned elements (options, metadata, difficulty levels).

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?

States a specific verb ('search and retrieve') and resource ('curriculum-aligned examination questions') and names the exam bodies covered (WAEC, JAMB, NECO). It does not distinguish itself from siblings such as aloc_find_similar_questions or aloc_get_session_questions, which an agent must resolve on its own.

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?

The description offers no when-to-use or when-not-to-use guidance and never mentions the sibling tools that could retrieve questions by another route. The only contextual note is the credit cost, which informs cost/benefit but not tool selection.

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