Skip to main content
Glama

面灵AI 面试助手

list_knowledge_bases

Read-only

列出用户的面试知识库:ID、名称、来源(custom 手写 / file 文件 / ai 生成)、问答条数、正文字数。知识库在面试时挂载,让面试助手的回答贴合用户的个人背景。(需要用户授权,范围 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.5/5.0
Behavior3/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 genuinely useful context beyond that: the required authorization scope interviews:read and the purpose of knowledge bases during interviews. It does not describe pagination or ordering, which is a moderate gap for a list operation.

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?

It is compact and front-loads the returned fields, then adds purpose, then the authorization note. Every sentence carries information, though the field enumeration and the interview-context sentence could arguably be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description usefully compensates by naming the returned fields and the auth scope. What is missing is any relationship to the sibling listing tools, which matters given a catalog full of knowledge-base and list_* tools.

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 the baseline is 4; there is nothing for the description to clarify beyond what the empty schema states.

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 (列出用户的面试知识库) and enumerates the returned fields (ID, name, source, Q&A count, word count). It does not distinguish this from the sibling list_official_knowledge_bases, so an agent cannot tell from the text alone which listing to pick.

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: it is a listing tool for the user's own knowledge bases. There is no explicit statement of when to use this versus list_official_knowledge_bases or get_knowledge_base, and no exclusions.

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