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

ALOC Model Context Protocol (MCP) Server

Official
by MaSSTeck

aloc_create_assessment_session

Initializes a timed, cheat-resistant assessment session for live candidate testing, generating subject- and exam-specific questions within a two-hour lifecycle.

Instructions

Initialize a timed candidate assessment session (2-hour lifecycle) for secure, cheat-resistant live test delivery. Consumes 5 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>",
      "examType": "<examType>"
    },
    "name": "aloc_create_assessment_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoDeterministic student candidate seed
countNoNumber of questions to assemble
presetNoStandard syllabus preset
subjectYesSubject name
examTypeYesExamination body
contentSourceNoContent provenance filter. Defaults to historical past questions; pass synthetic or all to explicitly include AI-generated questions.historical
shuffleOptionsNoWhether to shuffle option distractors

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.13

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description still discloses meaningful behavior: a 2-hour session lifecycle, a secure/cheat-resistant delivery context, and a 5-credit cost. It stops short of covering permission requirements, failure behavior when credits are insufficient, or what happens after session creation.

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?

The definition is two front-loaded sentences with no wasted wording. The first states purpose, lifecycle, and delivery context; the second states the credit cost.

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 description covers the core purpose, session duration, and credit consumption, but with no output schema it does not explain what is returned, such as a session identifier or expiration details. For a session-creation tool with no annotations, that leaves notable context gaps.

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?

The input schema has 100% description coverage across all 7 parameters, so the schema already carries the parameter semantics. The description adds no additional explanation of subject, examType, seed, count, preset, contentSource, or shuffleOptions, making the baseline score of 3 appropriate.

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, "Initialize", and a specific resource, "assessment session", with scope for timed live test delivery. It does not explicitly distinguish this from sibling aloc_generate_assessment, so it falls short of a 5.

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 "live test delivery" and the credit cost, but the description gives no explicit when-to-use guidance versus alternatives such as aloc_generate_assessment. There are also no stated exclusions or prerequisites beyond consuming credits.

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