Skip to main content
Glama

AceRound AI Interview Copilot

get_knowledge_base

Read-only

Read one interview knowledge base: name, the start of its text with total length, and an overview of its Q&A entries (one per line). The ID comes from list_knowledge_bases. Pass contentOffset to read long text 4000 characters at a time, or entryIds for full Q&A entries. (Requires the user's sign-in with scope interviews:read.)

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": "get_knowledge_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesKnowledge base ID
entryIdsNoEntry IDs to read in full
contentOffsetNoCharacter offset into the text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds context the annotations cannot: an explicit auth requirement for the interviews:read scope, the truncation behavior (returns only the start of the text plus total length), and the 4000-character paging window.

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 tight sentences, front-loaded with the resource and return shape, then the ID source, then the two optional-parameter modes, with auth in parentheses at the end. Nothing is redundant with the title or schema.

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?

With no output schema, the description takes on the return-value burden and does so reasonably, describing the truncated text plus length and the entry overview format. Minor gaps remain, such as error behavior for invalid IDs or the 30-item cap on entryIds, but an agent has enough to call it correctly.

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%, so a baseline of 3 applies, but the description genuinely adds meaning: it explains the ID's provenance, frames contentOffset as a 4000-character paging stride rather than a bare offset, and clarifies that entryIds switches the response to full entries.

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 (read) and resource (one interview knowledge base), and enumerates what comes back: name, text start with total length, and a one-per-line Q&A overview. The phrase 'interview knowledge base' plus the pointer to list_knowledge_bases separates it from sibling reads such as get_official_knowledge_base.

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 concrete routing: the ID comes from list_knowledge_bases, contentOffset is for paging long text 4000 characters at a time, and entryIds is the path to full Q&A entries. It does not state when not to use it (e.g. versus the official knowledge base getter), which keeps it short of a 5.

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