Skip to main content
Glama

面灵AI 面试助手

learn_answer_style

从一场面试记录中学习用户本人的回答风格,生成一段风格要求文字,可作为发起面试时的「额外回答要求」使用。面试 ID 取自 list_answer_style_sources。(需要用户授权,范围 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": {
      "interviewId": "<interviewId>"
    },
    "name": "learn_answer_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
interviewIdYes面试 ID,取自 list_interviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-vs-read question is settled structurally. The description adds genuinely useful non-annotated context: it requires user authorization with the interviews:write scope, and it discloses that a derived style text is produced. It does not say whether an existing learned style is overwritten, whether the learned result persists server-side, or how long generation takes, which keeps it at a 3 for a mutation tool.

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?

Two compact sentences, front-loaded with the purpose and output artifact, then the authorization requirement in parentheses. Every clause carries information; nothing is padded. The only cost is that the source-tool pointer is embedded mid-sentence rather than separated, which is exactly where the schema conflict occurs.

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 one-parameter tool with no output schema, the description covers what it consumes, what it produces, and the authorization scope needed to call it — enough for an agent to invoke it correctly. It is docked only because the provenance of interviewId is stated two different ways between description and schema, which an agent must resolve before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single interviewId parameter, so the baseline is 3. The description attempts to add provenance but does so inconsistently: it says the ID comes from list_answer_style_sources while the schema's own parameter description says it comes from list_interviews. That conflicting pointer adds confusion rather than meaning, so no credit above baseline.

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 names a specific verb+resource pair ('learn the user's answer style from an interview record') and states the concrete artifact produced ('a style-requirement text usable as extra answer requirements when starting an interview'). That is far more than a restatement of the name. It stops short of a 5 because it never positions itself against the closest siblings (edit_learned_profile_answer, delete_learned_profile_answer), leaving the agent to infer the distinction.

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?

Usage context is explicit: this is the tool to call when you need a reusable style requirement derived from an existing interview, and the interview ID is sourced from list_answer_style_sources. There are no exclusions ('do not use if a profile already exists') and no prerequisite ordering guidance, so it is clear context without alternatives.

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