Skip to main content
Glama

AceRound AI Interview Copilot

list_question_predictions

Read-only

List the user’s question predictions: record ID, role, company, created time, status (generating / done / failed) and number of questions. (Requires the user's sign-in with scope interviews:read.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_question_predictions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the required sign-in and the 'interviews:read' scope, plus the per-record status vocabulary (generating / done / failed), which tells the agent results may be incomplete. It stops short of describing ordering, result limits, or how a 'generating' record should be handled.

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?

A single front-loaded sentence with the core purpose first, the returned fields as a compact list, and the auth requirement in a trailing parenthetical. No filler, no restatement of the tool name, and nothing an agent would want trimmed.

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?

With no output schema available, the description carries the return-shape burden and does so by enumerating the exact fields plus the status enum values. With zero parameters and full annotation coverage, remaining gaps (ordering, truncation, behavior on failed records) are minor but non-zero.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The one meaningful implicit constraint — that results are scoped to the authenticated user — is conveyed by 'the user's', which is useful framing for a parameterless call.

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 and resource ('List the user's question predictions') and even enumerates the fields returned (record ID, role, company, created time, status, question count), which makes the scope unambiguous. It does not explicitly contrast itself with get_question_prediction or the start/save siblings, so differentiation is only implied by the list-vs-singular naming.

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 rather than stated: an agent can infer this is the enumeration tool for the current user's predictions, and the parenthetical establishes the required 'interviews:read' scope as a prerequisite. There is no explicit when-to-use/when-not guidance, no note that this returns only the signed-in user's records (as opposed to, say, all records), and no pointer to get_question_prediction for single-record retrieval.

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