Skip to main content
Glama

AceRound AI Interview Copilot

update_knowledge_base

Rename an interview knowledge base or replace its text; fields you omit stay unchanged. Passing content replaces the whole text. The ID comes from list_knowledge_bases. (Requires the user's sign-in with scope 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
idYesKnowledge base ID
nameNo
contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds the genuinely useful behavioral detail that passing content replaces the entire text, and that unspecified fields are preserved. It also discloses the required OAuth scope, which annotations do not cover. It does not say what happens to existing entries when content is overwritten, which would be the last missing piece for a mutation tool.

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 sentences, front-loaded with the core action and the most consequential semantic ('Passing content replaces the whole text'). The auth note is correctly parenthesized at the end. No sentence is redundant.

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?

With no output schema, the description still covers the mutation model, the ID source, and the permission requirement, which is enough to call the tool safely. The only gap is the absence of guidance on when to prefer the entry-level sibling over this 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% (only id is documented), so the description must compensate, and it does: it explains the ID's origin, that name performs the rename, and that content is a wholesale replacement rather than an append. Length limits and other constraints remain in the schema, which is acceptable.

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 ('Rename an interview knowledge base or replace its text'), which precisely captures the two mutation modes of this tool. It does not, however, name or distinguish itself from the close sibling update_knowledge_base_entry, so the whole-base vs single-entry boundary is left to inference from the name.

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 concrete context for calling it: partial-update semantics ('fields you omit stay unchanged'), the source of the required ID ('comes from list_knowledge_bases'), and the auth prerequisite. It stops short of explicit exclusions, e.g. that single entries should be changed with update_knowledge_base_entry rather than this tool.

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