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

ALOC Model Context Protocol (MCP) Server

Official
by MaSSTeck

aloc_get_question_explanation

Fetch step-by-step breakdowns, remedial hints, and AI-generated conceptual explanations for a specified question.

Instructions

Retrieve step-by-step breakdown, remedial hints, and AI-generated conceptual explanations for a specific question. Consumes 10 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": {
      "questionId": "<questionId>"
    },
    "name": "aloc_get_question_explanation"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoExplanation granularitystep_by_step
questionIdYesUUID of the question

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.13

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add one genuinely valuable behavioral fact — that each call consumes 10 ALOC credits — which materially affects invocation decisions. However, it says nothing about whether the result is cached, what happens when a question has no explanation, or what shape the response takes.

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 sentences, no filler, with the capability front-loaded and the cost constraint placed immediately after. Every clause carries information an agent needs.

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?

This is a simple read tool with full schema coverage and no output schema, and the credit cost is disclosed. Still missing are the failure modes (invalid UUID, missing explanation, insufficient credits) and any description of the returned content structure, which the absent output schema leaves to the description.

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 only two parameters, so the schema already documents questionId and the depth enum with its default. The description's mention of 'step-by-step' and 'remedial' loosely echoes two of the three depth values but adds no guidance on choosing between step_by_step, concise, and remedial — baseline 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?

States a specific verb ('Retrieve') and resource ('step-by-step breakdown, remedial hints, and AI-generated conceptual explanations for a specific question'), which is clearly distinguishable from search-oriented siblings like aloc_search_questions or aloc_find_similar_questions. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

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 only implied: an agent can infer you call this when you already have a questionId and need an explanation. There is no statement of when not to use it, no alternative named for related needs (e.g. finding a question in the first place), and no prerequisites such as needing a valid UUID or sufficient balance.

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