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

ALOC Model Context Protocol (MCP) Server

Official
by MaSSTeck

aloc_find_similar_questions

Find conceptually similar or variant examination questions by semantic vector similarity using a source question ID, with optional result limits.

Instructions

Find conceptually similar or variant examination questions using semantic vector similarity. 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_find_similar_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of similar questions to return (max 10, default 3)
questionIdYesUUID of the source 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?

With no annotations, the description carries the full behavioral burden, and it does disclose a concrete cost of 10 ALOC credits, which is genuinely useful pre-invocation context. It says nothing about permissions, whether results span subjects/difficulty, ranking or score behavior, or failure modes such as an invalid questionId.

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 with no filler; the core purpose is front-loaded and the credit cost is stated compactly at the end. 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should ideally indicate what comes back — question texts, similarity scores, ordering — which it does not. For a simple two-parameter read tool the purpose and cost are adequately covered, but the return-value gap keeps it at minimum viable.

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 parameters (questionId UUID, limit default 3 max 10) are already fully documented in the schema. The description adds no additional meaning about the parameters, 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 names a specific verb and resource (find similar/variant examination questions) and adds the mechanism (semantic vector similarity), which tells an agent this is a similarity lookup rather than a keyword search. It does not explicitly contrast itself with the sibling aloc_search_questions, so the distinction from the keyword-based alternative is left implicit.

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: the agent can infer it applies when it already holds a source questionId and wants variants. There is no explicit when-to-use/when-not guidance and no named alternative for keyword or exact-match retrieval, despite a plausible overlap with aloc_search_questions.

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