Skip to main content
Glama

面灵AI 面试助手

get_question_bank_question

Read-only

查看题库中一道题的详情:题干、参考解析、分类、被问次数、问过的公司与岗位、其他问法。题目 ID 取自 search_interview_questions、draw_questions 等工具。参考解析需要用户登录授权,免费用户每天可查看的解析数量有限(已看过的题不重复计数),额度用完时返回 locked。

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_bank_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes题目 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses the behaviors an agent actually needs: 参考解析 requires login authorization, free users have a daily view quota, already-viewed questions are not re-counted, and the response returns 'locked' when the quota is exhausted. That is concrete, non-obvious operational context.

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?

Front-loaded with the return-field list, then the id source, then the access/quota caveat — a sensible ordering with no filler sentences. Every clause carries either scope, provenance, or gating information.

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?

With no output schema, the description compensates by enumerating the returned fields and by describing the 'locked' degraded response. For a one-parameter read tool this leaves nothing material an agent would need before calling it.

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% and there is a single parameter, so baseline would be 3. The description goes further by naming the upstream tools the id should be obtained from, adding provenance the schema cannot express.

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 ('查看题库中一道题的详情') and then enumerates exactly what detail is returned: 题干、参考解析、分类、被问次数、问过的公司与岗位、其他问法. This distinguishes it clearly from sibling retrieval tools like search_interview_questions and draw_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?

Explicitly tells the agent where the required id comes from ('题目 ID 取自 search_interview_questions、draw_questions 等工具'), which establishes this as the follow-up detail call after a search or draw. It does not spell out when *not* to use it, but the positioning is clear enough in context.

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