Skip to main content
Glama

面灵AI 面试助手

list_question_predictions

Read-only

列出用户的押题(题库定制)记录:记录 ID、岗位、公司、生成时间、状态(generating 生成中 / done 完成 / failed 失败)与题数。(需要用户授权,范围 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.8/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds two things beyond that: the required auth scope (interviews:read) and the meaning of the status values (generating/done/failed), which tells an agent how to interpret results without extra calls.

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?

It is a single front-loaded sentence that names the resource first and then the fields returned; the auth note is correctly placed at the end in parentheses. The field enumeration is dense but each item earns its place by substituting for a missing output schema.

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 input parameters and no output schema, the description carries the burden of describing the return shape, and it does so (ID, position, company, generation time, status, question count). Pagination or result-limit behavior is not mentioned, which is the main remaining gap for a list tool.

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?

There are zero input parameters, so the baseline is 4 and there is nothing in the schema for the description to compensate for. No parameter guidance is needed, and none is given.

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 plus resource: it lists the user's 押题 (question-bank customization) prediction records, not a single record or a company list, which separates it from get_question_prediction and list_question_bank_companies. It does not name a sibling alternative explicitly, so it falls short of full differentiation.

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 by the phrase '用户的' (the current user's records); the description never states when to call this versus get_question_prediction or the other list_* tools. It does add a real prerequisite — the interviews:read authorization scope — which is genuinely useful before invocation.

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