Skip to main content
Glama

面灵AI 面试助手

save_questions_to_knowledge_base

把题库中选中的题目连同参考解析新建为一份面试知识库,真实面试时面试助手可直接使用。题目 ID 取自 search_interview_questions 等工具,一次最多 30 道;没有参考解析的题不会加入,与查看解析共用每日额度,因额度不足未加入的题数在 locked 中返回。(需要用户授权,范围 interviews:write)

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": {
      "ids": "<ids>"
    },
    "name": "save_questions_to_knowledge_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world write, and the description usefully adds operational context beyond them: max 30 IDs, questions lacking reference analyses are silently skipped, daily quota is shared with analysis viewing, and skipped counts come back in a locked field, plus the required interviews:write scope. Missing is any statement about whether an existing knowledge base is created or overwritten and what the primary return value is.

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?

One dense but well-ordered passage: purpose first, then ID source and limits, then skip/quota semantics, then authorization scope. Every clause carries distinct information and nothing is repeated from the schema or annotations.

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 a one-parameter mutation with no output schema, the description covers authorization, item limits, partial-failure semantics, and quota interaction, which is what an agent needs to call it safely. It stops short of describing the successful return payload (e.g., the new knowledge base identifier), a minor gap given no output schema exists.

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 0%, but the single ids parameter is covered well: the description explains where IDs come from (search_interview_questions), that they refer to question-bank entries, the 30-item cap, and the skip rule for questions without reference analyses. The only gap is that it never says whether IDs are question IDs or something else at the format level.

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?

States a specific verb and resource: creating a new interview knowledge base from selected question-bank questions plus reference analyses, usable by the interview assistant in real interviews. It also names the source tool (search_interview_questions), so an agent can distinguish it from generic knowledge-base creation tools, though it does not explicitly contrast with the close sibling save_question_prediction_to_knowledge_base.

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?

Gives clear context for when to use it: gathering selected questions with reference analyses into a knowledge base for live interviews, with IDs sourced from search_interview_questions and similar tools. It does not state when to prefer the prediction-based sibling or other knowledge-base creation paths, so routing between near-identical siblings is left to inference.

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