Skip to main content
Glama

面灵AI 面试助手

create_knowledge_base

新建一份面试知识库,可附带一段自由正文(项目介绍、个人经历等)。返回知识库 ID,之后可用 add_knowledge_base_entry、import_knowledge_base_entries 添加问答。(需要用户授权,范围 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": {
      "name": "<name>"
    },
    "name": "create_knowledge_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
contentNo自由正文

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?

Annotations already declare this is a non-read-only, non-destructive, non-open-world write. The description adds material context beyond them: it returns a knowledge base ID that later calls depend on, and it requires user authorization with the interviews:write scope. It does not discuss limits such as duplicate names or the 90000-char content cap, but the authorization and return-value notes are genuinely useful.

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?

Two compact sentences plus a trailing authorization note, with the primary action front-loaded and the follow-up tool guidance second. No filler or redundant restatement of the tool name.

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 supplies the return value (knowledge base ID), notes the permission scope, and points at the sibling tools needed to make the object useful. For a simple two-parameter creation tool, nothing an agent needs to invoke it correctly is missing.

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 coverage is only 50%, so the description must carry weight for the undocumented fields. It explains the optional content parameter with concrete examples (project introduction, personal experience) but never explicitly characterizes 'name' beyond the act of creating a knowledge base, and adds no format or constraint detail. This is adequate but leaves one parameter implicitly defined.

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 states a specific verb and resource ('新建一份面试知识库') and scopes it by noting the optional free-form body, so an agent can immediately tell this creates a knowledge base container rather than populating one. It further separates itself from siblings by naming add_knowledge_base_entry and import_knowledge_base_entries as the follow-up tools for adding Q&A.

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?

The description gives clear usage context: use this to create the knowledge base first, then use the named entry-adding tools afterward. It does not spell out explicit exclusions (e.g., when to prefer import_knowledge_base_entries from the start), but the sequencing guidance is unambiguous.

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