Skip to main content
Glama

面灵AI 面试助手

draw_questions

Read-only

从题库抽一组题用于刷题:random 为随机抽取,real 为按真实出现频次抽取。返回题目 ID 与题干,参考解析用 get_question_bank_question 逐题查看。

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": "draw_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNorandom = 随机,real = 按真实频次random
sizeNo抽取题数
companyNo公司名
keywordNo题目关键词
categoryNo题目分类
positionNo岗位,如「后端开发」「算法」
employmentTypeNo招聘类型,如「校招」「实习」「社招」
interviewRoundNo面试轮次,如「一面」「二面」「HR面」

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds that the result is a set of question IDs and stems, which is valuable because there is no output schema. It does not disclose what happens when filters match fewer questions than the requested size, or that size is capped, leaving some behavioral gaps.

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 dense line that front-loads the action, then the mode semantics, then the return shape and follow-up tool. Nothing is redundant or padded; every clause carries information an agent needs before calling.

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 an 8-optional-parameter, all-defaults sampling tool with no output schema, the description covers the core action, the mode choice, and what is returned (IDs and stems). The remaining gap is filter interaction and undersized-result behavior, which is not fatal for a read-only practice tool.

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 baseline is 3. The one piece of parameter meaning in the description (random vs. real frequency sampling) merely restates the schema's own enum description, and nothing is said about how the eight optional filters (company, keyword, category, position, etc.) combine or whether they are ANDed.

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 gives a concrete verb and resource ("从题库抽一组题") plus the use case ("/用于刷题"), so an agent immediately knows this samples questions from the question bank for practice. It names get_question_bank_question as the follow-up for explanations, but does not contrast itself with other drawing/search siblings such as draw_interview_session or search_interview_questions.

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?

Usage context is explicit (practice drilling) and the two sampling modes are explained so the agent can pick one. It also routes the agent to get_question_bank_question for per-question explanations, which is a genuine alternative pointer, but there is no statement of when NOT to use this tool (e.g. versus a search or interview-session tool).

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