Skip to main content
Glama

AceRound AI Interview Copilot

create_knowledge_base

Create an interview knowledge base, optionally with free text (project notes, experience). Returns its ID; add Q&A with add_knowledge_base_entry or import_knowledge_base_entries. (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": {
      "name": "<name>"
    },
    "name": "create_knowledge_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
contentNoFree text

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 it is a non-destructive, non-read-only, closed-world write. The description adds two things the annotations do not: the return value (its ID, needed to chain follow-up calls) and an explicit auth requirement (sign-in with scope interviews:write).

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 sentences, front-loaded with the action, then the follow-up path, then a parenthetical auth note. No filler, and the chaining information is placed before the secondary permission detail.

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 two-parameter creation tool with annotations covering the safety profile and no output schema, the description covers action, optional payload, return value, next-step tooling, and auth scope. 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 50%: 'content' is only labeled 'Free text' and 'name' has no description at all. The description compensates by explaining that the optional content is free-form project notes or experience, which tells the agent what to put there; the required 'name' remains defined only by its schema constraints.

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 ('Create an interview knowledge base') and immediately clarifies the optional content shape with examples (project notes, experience). It also names the follow-up tools, so an agent can tell create apart from add_knowledge_base_entry / import_knowledge_base_entries without opening any schema.

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 clear next-step routing: Q&A content goes through add_knowledge_base_entry or import_knowledge_base_entries rather than this tool. There is no explicit 'when not to use' or prerequisite ordering beyond the auth note, but for a creation tool this is a solid contextual frame.

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