Skip to main content
Glama

面灵AI 面试助手

update_knowledge_base

修改一份面试知识库的名称或正文;只传要改的字段,未传的保持原样。传 content 会整段替换原正文。知识库 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": {
      "id": "<id>"
    },
    "name": "update_knowledge_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes知识库 ID
nameNo
contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false. Beyond that, the description discloses the two behaviors that most affect a caller: partial-update semantics ('未传的保持原样') and the fact that passing content wholesale replaces the existing body ('整段替换原正文'), plus the required authorization scope interviews:write. Return values and failure modes are not described.

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?

Four short clauses, front-loaded with the action and immediately followed by the two constraints that determine correct invocation. No filler; the authorization note is compact and last, which is the right position for it.

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 three-parameter mutation tool with no output schema, the description covers partial-update behavior, the destructive-scope replacement of content, the ID source, and the auth scope. Only the response shape and name-field constraints are left unaddressed, which is minor for a tool of this size.

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 description coverage is only 33% — only 'id' is documented in the schema, while 'name' and 'content' have no field descriptions. The description partially compensates by explaining that content is a full replacement and that both fields are optional, but it adds no meaning for 'name' (length bounds, uniqueness, renaming rules), leaving a real gap.

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?

The description names a specific verb and resource plus the exact mutable fields: '修改一份面试知识库的名称或正文'. The phrase '一份面试知识库' (a knowledge base itself) implicitly separates it from update_knowledge_base_entry, which targets entries, but no sibling is named outright, so differentiation is inferred rather than stated.

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 clear operating context: pass only the fields to change, omitted fields stay unchanged, and the ID comes from list_knowledge_bases — an explicit prerequisite chain. What's missing is when NOT to use it (e.g., to change an individual entry, use update_knowledge_base_entry).

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