Skip to main content
Glama

AceRound AI Interview Copilot

list_knowledge_bases

Read-only

List the user’s interview knowledge bases: ID, name, source (custom / file / ai), number of Q&A entries and text length. Knowledge bases are attached to an interview so the assistant’s answers fit the user’s background. (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_knowledge_bases"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 establish this as a safe, closed-world read, so the description's added value is the auth prerequisite (sign-in with scope interviews:read) and the shape of what comes back. That is real context beyond the structured fields. It stops short of noting pagination, ordering, or what an empty list means.

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: what it returns, why it matters, and the auth caveat. Purpose and returned fields are front-loaded with no filler. The parenthetical auth note is slightly tacked on but still earns its place.

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 zero-parameter read with no output schema, the description compensates well by listing the returned fields and stating the required auth scope. Nothing essential is missing, though a pointer to the official-list sibling would make the choice between the two unambiguous.

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 no parameters, so the baseline is 4 and there is nothing the description needs to disambiguate. It correctly avoids inventing filter options the schema does not support.

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 gives a specific verb and resource ("List the user's interview knowledge bases") and even enumerates the fields returned (ID, name, source, Q&A count, text length). It implicitly scopes to the user's own bases, which separates it from list_official_knowledge_bases, but it never names or explicitly contrasts that sibling.

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 only implied through the note that knowledge bases are attached to an interview so answers fit the user's background. There is no explicit when-to-use statement, no when-not to use it, and no named alternative for the official/catalog variant.

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