Skip to main content
Glama

AceRound AI Interview Copilot

add_knowledge_base_entry

Add one Q&A entry (question + reference answer) to an interview knowledge base. The ID comes from list_knowledge_bases; returns the entry ID. (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>",
      "question": "<question>",
      "answer": "<answer>"
    },
    "name": "add_knowledge_base_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerYes
questionYes
materialIdYesKnowledge base ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write. The description adds value beyond that by disclosing the required auth scope (interviews:write) and that the call returns the new entry ID, which the annotations do not cover.

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 action and payload, followed by the ID source, return value, and auth requirement. No redundant or filler text.

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

Completeness5/5

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

For a simple 3-parameter write tool with no output schema, the description covers the action, input sourcing, return value, and permission requirement. Nothing an agent needs to invoke it correctly is missing.

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 materialId is documented), so the description must compensate. It does so by explaining that materialId is a knowledge base ID sourced from list_knowledge_bases and by mapping 'question + reference answer' to the question and answer parameters.

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?

States a specific verb and resource ('Add one Q&A entry ... to an interview knowledge base') and clarifies the payload shape (question + reference answer), which distinguishes it from bulk siblings like import_knowledge_base_entries and generate_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 Guidelines4/5

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

Gives a concrete prerequisite: the materialId must come from list_knowledge_bases, which tells the agent how to obtain the required input. It does not explicitly exclude alternatives (e.g., bulk import or generation), so it falls short of full when/when-not guidance.

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