Skip to main content
Glama

AceRound AI Interview Copilot

generate_knowledge_base_entries

Have AI predict interview questions from the user’s resume and/or target role and append them with reference answers to a knowledge base (8 by default, up to 15). Knowledge base ID from list_knowledge_bases, resume ID from list_resumes; give at least one of resume or role. Returns how many entries were added. (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>"
    },
    "name": "generate_knowledge_base_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
countNo
goalIdNo
resumeIdNo
materialIdYes

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?

Goes well beyond the annotations: discloses the sign-in scope requirement (interviews:write), that entries are appended rather than overwriting, the default/cap on generated entries, and that it returns a count added. What is missing is any note on the AI-generated content's accuracy or whether duplicates are prevented.

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?

Effect and scaling are front-loaded, followed by the ID-source prerequisites, the return value, and the auth note in a compact parenthetical. Three dense clauses with no filler; only the trailing auth parenthetical slightly interrupts the flow.

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?

A mutating, AI-driven generation tool with no output schema — the description compensates by stating the return value, the write scope, and the entry cap. It would be complete if it clarified what the required materialId represents and whether repeated runs append duplicates.

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 0%, so the description must carry all parameter meaning. It explains count well ('8 by default, up to 15') and maps resume/role to their ID sources, but the required materialId and the lang parameter are never mentioned, leaving the one mandatory field undocumented.

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 concrete verb and outcome: AI predicts interview questions from resume/target role and appends them with reference answers to a knowledge base. The resource and effect are unmistakable. It doesn't distinguish itself from the close sibling save_question_prediction_to_knowledge_base, so it stops short of a 5.

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 real precondition — 'give at least one of resume or role' — and points to the prerequisite lookup tools (list_knowledge_bases, list_resumes) for obtaining IDs. It lacks an explicit exclusion or routing note versus add_knowledge_base_entry/save_question_prediction_to_knowledge_base, so it is clear context rather than 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