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

ALOC Model Context Protocol (MCP) Server

Official
by MaSSTeck

aloc_get_coverage_matrix

Check live examination, subject, and paper-year availability across JAMB, WAEC, NECO, and Post-UTME before querying questions; free to use.

Instructions

Retrieve live examination, subject, and paper-year availability across JAMB, WAEC, NECO, and Post-UTME before querying questions. 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_coverage_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.13

TDQS

A4.1/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 disclosure burden. It usefully adds two behavioral facts beyond the schema: the data is 'live' (freshness) and the call is 'Free (0 credits)' (cost, relevant given the sibling aloc_check_credit_balance), but it says nothing about response shape, size, caching, or failure modes.

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?

A single sentence with the resource named first, scope second, and the cost/ordering caveats trailing. Every clause carries information; nothing is repeated from the schema or title.

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?

For a zero-argument discovery tool with no output schema, the description establishes what domain is covered but not what the returned matrix looks like (per-exam nesting? availability flags? subject lists?). An agent knows when to call it but must call it blind regarding the return structure.

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 nothing for the description to disambiguate; baseline 4 applies. The description correctly adds no parameter commentary, avoiding noise.

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?

The description opens with a specific verb and resource ('Retrieve live examination, subject, and paper-year availability') and enumerates the exact exam boards covered (JAMB, WAEC, NECO, Post-UTME). An agent can tell what this returns and how it differs from question-querying siblings without opening any schema.

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?

It gives a clear ordering instruction ('before querying questions'), which defines the correct point in the workflow to call it. It does not name a specific alternative sibling or state when the tool should be skipped, so it stops short of full when/when-not guidance.

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