Skip to main content
Glama

面灵AI 面试助手

save_question_prediction_to_knowledge_base

把一次押题的全部题目与作答思路新建为一份面试知识库,真实面试时面试助手可直接使用。记录 ID 取自 list_question_predictions,返回新知识库 ID。(需要用户授权,范围 interviews:write)

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": "save_question_prediction_to_knowledge_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes押题记录 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, non-destructive, closed-world write. The description adds genuinely new behavior: it requires user authorization with the interviews:write scope, and it returns the new knowledge base ID. It does not say what happens if a knowledge base already exists for that prediction record.

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?

Front-loaded with the action and the source data, followed by the ID provenance and the authorization scope. Every clause carries information; only the 'usable during a real interview' clause is closer to motivation than instruction, but it explains the downstream value.

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?

For a one-parameter write tool with annotations and no output schema, the description covers action, data source, ID provenance, downstream use, return value (new knowledge base ID), and the required auth scope. Nothing essential for correct invocation is missing.

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 coverage is 100% and the single parameter is documented as the prediction record ID, so the baseline is 3. The description adds real value by stating where that ID must come from (list_question_predictions), which prevents the agent from passing an arbitrary string.

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?

Uses a specific verb+resource: creating a new interview knowledge base from all questions and answer approaches of a single question-prediction record. It is distinguishable from the closest sibling save_questions_to_knowledge_base only by inference (it sources from one prediction record), not by explicit contrast.

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 prerequisite workflow pointer — the record ID comes from list_question_predictions — and notes the resulting knowledge base is usable by the interview assistant during a real interview. It offers no when-not-to-use guidance and never contrasts itself with save_questions_to_knowledge_base or create_knowledge_base.

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