Skip to main content
Glama

面灵AI 面试助手

generate_knowledge_base_entries

按用户的简历和 / 或目标岗位,由 AI 预测面试问题并写好参考答案,直接追加到指定知识库(默认 8 条,最多 15 条)。知识库 ID 取自 list_knowledge_bases,简历 ID 取自 list_resumes;简历与岗位至少给一个。返回新增条数。(需要用户授权,范围 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": {
      "materialId": "<materialId>"
    },
    "name": "generate_knowledge_base_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
countNo
goalIdNo
resumeIdNo
materialIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, it discloses that writes are appends only, that user authorization with scope interviews:write is required, that the default is 8 entries capped at 15, and that the return value is the number of added entries. That is real behavioral context the annotations do not provide, though failure modes (e.g., quota exhaustion, invalid materialId) are not covered.

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?

The core action and its output are front-loaded in the opening clause; the ID sources, constraints, return value, and auth scope follow in a compact sequence. It is dense but each clause carries information, with minimal redundancy.

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 non-destructive mutation tool with no output schema and five undocumented parameters, the description covers the action, inputs, limits, auth scope, and return value. Only the lang parameter remains unexplained, which is a minor but real omission.

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 description coverage is 0%, so the description must carry the load, and it largely does: materialId is identified as the knowledge base ID sourced from list_knowledge_bases, resumeId from list_resumes, goalId as the target position, and count gets a default of 8 and a cap of 15. The lang parameter is never mentioned, which is the one clear gap.

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?

The description names a specific verb and resource: AI generates interview questions plus reference answers and appends them to a designated knowledge base. It also states the generative mechanism (based on resume and/or target position), which distinguishes it from sibling entry-insertion tools such as add_knowledge_base_entry.

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?

It gives concrete preconditions: at least one of resume or goal must be supplied, knowledge base IDs come from list_knowledge_bases, and resume IDs come from list_resumes. It lacks an explicit 'when not to use this, use X instead' clause against the manual entry-adding siblings, so it falls short of full routing guidance.

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