Skip to main content
Glama

面灵AI 面试助手

add_knowledge_base_entry

向一份面试知识库添加一条预设问答(问题 + 参考答案)。知识库 ID 取自 list_knowledge_bases;返回条目 ID。(需要用户授权,范围 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>",
      "question": "<question>",
      "answer": "<answer>"
    },
    "name": "add_knowledge_base_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerYes
questionYes
materialIdYes知识库 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses an authorization requirement and its exact scope (interviews:write) plus the return value (entry ID). That is genuinely useful behavioral context an agent cannot get from the annotation flags alone; it stops short of describing validation failures or limits.

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?

A single dense sentence with parenthetical clauses, front-loaded with the action and resource, followed by the ID source, return value, and auth scope. Nothing is redundant, though the stacked parentheses make it slightly less scannable than a two-clause split.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 3-parameter mutation with no output schema, the description covers the action, ID provenance, return value, and auth scope, which is close to sufficient. It omits whether duplicate questions are rejected or what happens on authorization failure, leaving a small gap for a write tool.

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 only 33%, with just materialId documented, so the description must compensate. It does so by explaining that the two other fields are a question and a reference answer and by naming list_knowledge_bases as the source of materialId, adding meaning the schema does not contain (length bounds remain schema-only, which is fine).

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: add a preset Q&A pair (question + reference answer) into an interview knowledge base, and adds that it returns an entry ID. This clearly distinguishes creation from update/delete siblings, though it does not explicitly name the closest alternatives such as update_knowledge_base_entry or import_knowledge_base_entries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives one concrete usage prerequisite: the knowledge base ID comes from list_knowledge_bases, which tells the agent how to prepare the call. It offers no when-not-to-use guidance and no routing to alternatives for bulk or update scenarios, so usage is implied rather than fully framed.

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