Skip to main content
Glama

AceRound AI Interview Copilot

save_question_prediction_to_knowledge_base

Save all questions and answer outlines of a prediction as a new interview knowledge base the interview assistant can use live. The record ID comes from list_question_predictions; returns the new knowledge base 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": {
      "id": "<id>"
    },
    "name": "save_question_prediction_to_knowledge_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPrediction ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 operation, so the bar is lower. The description adds real context beyond them: a NEW knowledge base is created (not an in-place update), the result is the new KB ID, and the call requires the user's sign-in with the interviews:write scope. It does not say what happens on repeat calls for the same prediction.

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?

Three short sentences, front-loaded with the action and outcome, then the ID provenance, then the auth constraint. The parenthetical auth note is slightly tacked on but each clause carries distinct information.

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?

There is no output schema, but the description compensates by stating the return value is the new knowledge base ID. For a one-parameter creation tool with annotations covering the safety profile, the remaining gap is only behavior on duplicate or pre-existing knowledge bases.

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 100% for the single id parameter, so baseline is 3. The description adds meaning beyond the schema's 'Prediction ID' by pinning down which sibling tool produces a valid value, which materially reduces mis-invocation risk.

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 states a specific verb+resource transformation: take all questions and answer outlines of a prediction and persist them as a new interview knowledge base. That is far more informative than the name alone and distinguishes it from create_knowledge_base by scoping the source to a prediction. It stops short of an explicit contrast with start_question_prediction, which touches the same prediction record.

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?

It tells the agent the prerequisite source of the ID (list_question_predictions), which is genuine usage guidance for invocation ordering. However, it gives no when-to-use/when-not guidance relative to the adjacent tools that also act on predictions or create knowledge bases.

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