Skip to main content
Glama

面灵AI 面试助手

get_knowledge_base

Read-only

查看一份面试知识库:名称、正文开头与总字数、问答条目概览(每行一条)。知识库 ID 取自 list_knowledge_bases。正文较长时传 contentOffset 分段读取(每段 4000 字);传 entryIds 返回这些条目的完整问答。(需要用户授权,范围 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
idYes知识库 ID
entryIdsNo要查看完整问答的条目 ID
contentOffsetNo从正文第几个字开始读取

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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, and the description adds value on top: it discloses the authorization requirement and scope (interviews:read) and the 4000-character segmentation behavior for long bodies. It does not cover error behavior or what happens when entryIds exceed the 30-item cap, which keeps 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.

Conciseness5/5

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

A single compact paragraph with the resource and return shape front-loaded, followed by the ID source, then the two paging modes, then the auth scope. Every clause carries distinct information with no repetition of the schema or annotations.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does so by naming the fields returned and the overview format. Combined with the ID source, pagination rule and auth scope, an agent has everything needed to invoke it correctly; the entryIds maximum is already in the schema.

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 description coverage is 100%, so baseline would be 3, but the description earns above baseline by explaining the operational meaning of contentOffset (chunk size of 4000 characters, implying repeated paging) and of entryIds (returns full Q&A for those entries rather than the overview). These are behavioral semantics the schema field descriptions do not convey.

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 (查看一份面试知识库) and enumerates exactly what is returned: name, body opening plus total character count, and a one-line-per-entry Q&A overview. The qualifier 面试 (interview) distinguishes it from the official knowledge-base sibling, and the ID provenance is stated, so an agent can identify the tool without opening the schema.

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 usage routing: the ID comes from list_knowledge_bases, contentOffset should be used when the body is long, and entryIds should be used when full Q&A text is needed. It stops short of explicitly excluding or contrasting alternatives such as get_official_knowledge_base, so it is clear context rather than a full when/when-not decision rule.

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