Skip to main content
Glama

AceRound AI Interview Copilot

import_knowledge_base_entries

Bulk-import Q&A entries (1–200 per call, appended) into an interview knowledge base. The ID comes from list_knowledge_bases; the batch is rejected if it would exceed the base’s capacity. (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>",
      "entries": "<entries>"
    },
    "name": "import_knowledge_base_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYes
materialIdYes

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?

Beyond the annotations (readOnly=false, destructive=false), it discloses that entries are appended rather than overwriting, that an entire batch is rejected if it would exceed capacity, and that the interviews:write scope sign-in is required. It does not address duplicate handling or whether a rejected batch leaves any partial state.

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?

Two tight sentences with the action and the size/append semantics front-loaded, followed by provenance, failure mode, and auth. The trailing parenthetical on auth is slightly tacked on but carries real 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?

For a write tool with annotations covering the safety profile and no output schema, the description covers limits, append semantics, ID provenance, capacity failure, and auth requirements. Only edge behaviors like duplicate entries and per-item validation failures are left unstated.

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 the load. It clarifies that materialId comes from list_knowledge_bases and restates the 1-200 batch bound, but adds nothing about the nested question/answer objects beyond what the schema's min/max lengths already encode.

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?

The description opens with a specific verb and resource ('Bulk-import Q&A entries ... into an interview knowledge base') and qualifies it as bulk (1-200, appended), which separates it from the singular add_knowledge_base_entry sibling. Scope and target object are 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 states the bulk context and points to list_knowledge_bases as the source of the materialId, and warns that over-capacity batches are rejected. It never explicitly says to use add_knowledge_base_entry for single entries, so the alternative routing is only implied by the 'Bulk' qualifier.

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