Skip to main content
Glama

面灵AI 面试助手

update_knowledge_base_entry

修改知识库中的一条问答;只传要改的问题或答案,未传的保持原样。条目 ID 取自 get_knowledge_base。(需要用户授权,范围 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>",
      "entryId": "<entryId>"
    },
    "name": "update_knowledge_base_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerNo
entryIdYes条目 ID
questionNo
materialIdYes知识库 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 two things the annotations do not: that unpasssed fields are preserved (a partial rather than wholesale overwrite), and that the call requires user authorization with scope interviews:write. It stops short of saying whether edits are reversible or versioned, so not a 5.

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 short clauses, front-loaded with the action and its partial-update rule, then the ID source, then the auth requirement. No filler or repetition; every sentence carries information the agent needs.

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 4-parameter mutation with no output schema, the description covers the essentials: what changes, what is preserved, where the ID comes from, and the authorization scope. It leaves open the relationship between entryId and materialId and any error/failure behavior, which is a minor gap rather than a blocker.

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?

With schema description coverage at 50%, the description compensates well for the two undocumented fields by stating that question and answer are optional and only supplied fields change. It also explains the provenance of entryId (obtained from get_knowledge_base). It adds nothing about materialId beyond the schema's "知识库 ID", and does not state that the entry must belong to that material, keeping it below a 5.

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: modify one Q&A entry inside a knowledge base. The phrase "一条问答" scopes it to an entry rather than the knowledge base container itself, which is the distinction that matters against siblings such as update_knowledge_base. An agent can identify the operation without opening the schema.

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?

Usage is implied rather than spelled out: it tells the agent this is a partial edit ("只传要改的问题或答案,未传的保持原样") and where the entry ID comes from (get_knowledge_base). However, it names no explicit alternative or when-not condition, e.g. when to use this versus update_knowledge_base or add_knowledge_base_entry. Adequate but with a clear routing gap.

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