Skip to main content
Glama

面灵AI 面试助手

list_official_knowledge_bases

Read-only

列出官方资料库:补充模型训练数据中缺失的近一年行业知识,持续更新,开始面试时可与用户自己的知识库一起直接挂载,无需导入。(需要用户授权,范围 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

A3.6/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, so the description's job is to add context — and it does, disclosing the required authorization scope (interviews:read) and the fact that the official bases are continuously updated and require no import. It stops short of describing return shape or how many bases come back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The auth requirement is usefully parenthesized at the end, but the middle clause about supplementing training data with the past year of industry knowledge is marketing framing that does not help an agent decide or invoke. Roughly a third of the text could be trimmed without loss.

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 output schema, the description is the only place to learn what a returned item looks like, and it only says these are official, continuously-updated knowledge bases — no field-level or cardinality hint. For a simple zero-param list tool with readOnly annotations this is adequate but not complete.

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; the baseline for a no-parameter tool is 4. No parameter-related claims are made or needed.

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?

States a specific verb and resource ('列出官方资料库' / list official knowledge bases) and distinguishes it from the user's own knowledge bases by stressing '官方' and the contrast with '用户自己的知识库'. The distinction from the sibling list_knowledge_bases is only implied, not named explicitly.

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?

Gives a usage context — these can be mounted alongside the user's own knowledge bases at the start of an interview with no import step — but never says explicitly when to call this versus list_knowledge_bases, nor does it state any 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