Skip to main content
Glama

AceRound AI Interview Copilot

update_knowledge_base_entry

Edit one Q&A entry; fields you omit stay unchanged. Entry IDs come from get_knowledge_base. (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": {
      "materialId": "<materialId>",
      "entryId": "<entryId>"
    },
    "name": "update_knowledge_base_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerNo
entryIdYesEntry ID
questionNo
materialIdYesKnowledge base ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, and the description usefully adds that omitted fields are preserved (partial update semantics) and that the call requires the user's sign-in with scope interviews:write. That auth and reversibility-adjacent detail is genuine value beyond the structured fields.

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?

Two short sentences, front-loaded with the action and the most consequential semantic (omitted fields persist), followed by ID provenance and the auth note. Nothing is wasted or buried.

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 four-parameter partial-update tool with no output schema, the description covers purpose, ID source, partial-update behavior, and permission scope. The only gap is the undocumented question/answer parameters, which the schema names adequately by convention.

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 coverage is only 50%: entryId and materialId are documented, but question and answer carry only length bounds. The description compensates partly by clarifying that any omitted field is left unchanged, which tells the agent the two content fields are optional in an update, but it adds no meaning about what question vs answer contain.

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 opens with a specific verb+resource pair, 'Edit one Q&A entry,' which clearly separates it from the add/delete siblings. It does not name an alternative tool explicitly, but the singular scope and 'edit' verb make the intent unambiguous.

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 establishes a clear prerequisite by stating entry IDs come from get_knowledge_base, and tells the agent this is a partial edit where omitted fields stay unchanged. It stops short of explicit when-not guidance or naming create/delete alternatives, so it is clear context rather than full routing.

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