Skip to main content
Glama

面灵AI 面试助手

import_knowledge_base_entries

向一份面试知识库批量导入问答(一次 1–200 条,追加在已有条目之后)。知识库 ID 取自 list_knowledge_bases;超出单库容量时整批拒绝。(需要用户授权,范围 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>",
      "entries": "<entries>"
    },
    "name": "import_knowledge_base_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYes
materialIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: entries are appended after existing ones (consistent with destructiveHint=false), the whole batch is rejected atomically if it exceeds library capacity, and the call requires user authorization with the interviews:write scope. Atomic failure and auth-scope disclosure are exactly the traits an agent needs before attempting a 200-entry write.

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?

Three tight sentences with the core action, the ID source, the failure mode, and the auth requirement, all front-loaded with no filler. Parenthetical clauses carry the size band and permission scope without bloating the text.

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 two-parameter write tool with annotations and no output schema, the description covers preconditions, ID sourcing, bounded batch size, and atomic rejection — enough to call it correctly. The one gap is that with no output schema, nothing describes what the agent gets back (e.g., count of imported entries) to confirm success.

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%, but the description compensates at the top level: it identifies the knowledge base ID as coming from list_knowledge_bases (mapping to materialId) and confirms the 1–200 batch bound that the schema encodes separately. It does not spell out the required question/answer fields inside each entry or note that materialId is the parameter name, leaving mild inference to the agent.

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 — batch importing Q&A pairs into an interview knowledge base — plus the batch size band (1–200) and append semantics. The word for batch (批量) combined with the range implicitly separates it from the single-entry sibling add_knowledge_base_entry and from create_knowledge_base, which creates the container rather than filling it.

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 operating context: the knowledge base ID is obtained from list_knowledge_bases, so the agent knows where to get materialId before calling. It does not explicitly say when to prefer this over add_knowledge_base_entry for a single entry, nor what to do when the target library is near capacity beyond noting the batch will be rejected.

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