Skip to main content
Glama

AceRound AI Interview Copilot

list_official_knowledge_bases

Read-only

List the official knowledge bases: recent industry knowledge missing from model training data, kept up to date. They can be attached to an interview alongside the user’s own knowledge bases without importing. (Requires the user's sign-in with scope interviews:read.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_official_knowledge_bases"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds context the annotations cannot: the auth requirement ('Requires the user's sign-in with scope interviews:read') and the notable behavior that attaching these bases requires no import step. Return shape and pagination are not covered, keeping it below a 5.

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 sentences, purpose front-loaded, and the auth constraint in a parenthetical that is easy to skip or scan. Slightly dense phrasing ('missing from model training data, kept up to date') costs a little, but nothing is redundant.

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 parameters, no nested objects, and no output schema, the burden on the description is modest, and it covers identity, intended use, and the auth prerequisite. The only gap is what a returned entry looks like, which matters little for a list tool whose primary job is discovery.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not waste space restating an empty schema.

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 ('List the official knowledge bases') and immediately qualifies what 'official' means — recent industry knowledge absent from model training data, maintained up to date. This implicitly separates it from the sibling list_knowledge_bases, which covers the user's own bases, so an agent can pick between them without opening a schema.

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?

Usage is implied rather than stated: the description explains these bases can be attached to an interview alongside the user's own without importing, which hints at when an agent would call it. It never explicitly says 'call this when you need X rather than list_knowledge_bases', and there are no exclusions or prerequisites beyond the auth scope.

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