Skip to main content
Glama

面灵AI 面试助手

get_question_prediction

Read-only

查看一次押题(题库定制)的状态与结果。记录 ID 取自 list_question_predictions 或 start_question_prediction。默认返回状态、总述与题目概览(每行一题);传 indexes 返回指定题目的考察点、作答思路与可用素材。状态为 generating 时返回当前进度,failed 时返回失败原因。(需要用户授权,范围 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
idYes押题记录 ID
indexesNo要查看全文的题目序号(从 1 开始)

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 establish readOnly/openWorld/destructive flags, and the description adds real context on top: the authorization requirement (interviews:read scope) and the state-dependent return behavior (progress while generating, failure reason when failed). It does not say whether a generating record must be polled or how often, which is the one remaining behavioral gap.

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?

Four compact clauses, front-loaded with purpose, then ID provenance, then output modes, then state handling and auth. Dense but every clause carries information; the parenthetical auth note at the end is slightly tacked-on but not wasteful.

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

Completeness5/5

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

No output schema exists, so the description carries the return-value burden — and it does, describing the default payload, the detailed payload, and the generating/failed variants. Combined with full schema coverage and existing annotations, an agent has everything needed to call this correctly.

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 both parameters are already documented; the description still adds meaning by contrasting default output (status, summary, per-line question overview) with the indexes path (examination points, answering approach, available materials). That clarifies the practical effect of the optional parameter rather than restating its type.

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+resource: view the status and results of one question-prediction record, and names the two sibling tools that produce the ID (list_question_predictions, start_question_prediction). An agent can distinguish it from list_question_predictions or delete_question_prediction without opening any schema.

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?

Explicitly tells the agent where the required id must come from (two named sibling tools) and explains the two invocation modes: default summary/overview versus passing indexes for full detail. It lacks an explicit 'do not use when…' exclusion, but the routing context is clear enough to select correctly.

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