Skip to main content
Glama

AceRound AI Interview Copilot

get_question_prediction

Read-only

Read one question prediction. The record ID comes from list_question_predictions or start_question_prediction. Returns the status and an overview with one question per line; pass indexes to read the why-asked, answer outline and material for those questions. (Requires the user's sign-in with scope interviews:read.)

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": {
      "id": "<id>"
    },
    "name": "get_question_prediction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPrediction ID
indexesNoQuestion numbers to read in full (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds meaningful context beyond them: the required sign-in scope interviews:read and the shape of the response (status plus one question per line, richer fields only for requested indexes). It does not cover failure modes such as a missing or unauthorized ID.

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?

Three tight sentences, front-loaded with the core action, followed by ID provenance, then the optional expansion behavior, then the auth requirement. No redundant restatement of the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

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

For a two-parameter read with no output schema, the description adequately conveys return structure (status + per-question overview + expanded detail) and the auth scope. Only minor gaps remain, such as what happens for invalid indexes or an ID the user cannot access.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns credit above it by explaining that indexes unlock the why-asked, answer outline and material for those questions, which is more than the schema's generic "Question numbers to read in full." It also explains where id originates, adding provenance the schema lacks.

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?

States a specific verb and resource ("Read one question prediction") and immediately distinguishes itself from siblings by naming list_question_predictions and start_question_prediction as the sources of the ID. An agent can tell this is the single-record fetch, not the list or create flow.

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?

Explains the prerequisite for the required ID (obtained from list_question_predictions or start_question_prediction) and states the condition for using the optional parameter: pass indexes when the full why-asked, answer outline and material are needed. No explicit when-not-to-use guidance, so it falls just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources