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

ALOC Model Context Protocol (MCP) Server

Official
by MaSSTeck

aloc_report_question_issue

Report typos, incorrect answer keys, or ambiguous wording on a specific ALOC question so quality moderators can review and correct the issue.

Instructions

Report a typo, incorrect answer key, or ambiguity on a specific question to ALOC quality moderation. Free (0 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>",
      "type": "<type>",
      "message": "<message>"
    },
    "name": "aloc_report_question_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesCategory of issue identified
messageYesDetailed description of the issue or mathematical discrepancy
questionIdYesUUID of the question with an issue
reporterNameNoOptional name of reporting agent or developer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.13

TDQS

A3.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden; it discloses the cost profile and the fact that the report is routed to human quality moderation. It leaves unstated what happens after submission (acknowledgement, tracking ID, whether the caller is contacted) and whether duplicate reports are deduplicated.

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 compact sentences with the purpose front-loaded and the cost caveat appended, with no filler. It is arguably slightly under-written for a state-changing report tool, but nothing is wasted.

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 4 well-documented parameters, full schema coverage, and no output schema, the description covers the essentials. However, for a submission tool that creates a moderation record, it says nothing about the outcome of the call or follow-up behavior, which is the main remaining gap.

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 the enum, message, questionId, and reporterName are already fully documented in the schema. The description's list of issue classes (typo, answer key, ambiguity) loosely maps onto the enum values but adds no new parameter-level semantics or format guidance.

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 ("Report") and a precise resource ("a typo, incorrect answer key, or ambiguity on a specific question"), and names the destination (ALOC quality moderation). It does not differentiate against any sibling, though none of the listed siblings appear to be competing reporting tools, so the omission is minor.

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?

It gives one useful decision input — the call is free (0 credits) — which helps an agent choose it without cost anxiety. It does not state when to use this versus working around an error, nor any exclusions (e.g., do not report the same question twice).

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