Skip to main content
Glama

面灵AI 面试助手

prepare_invited_interview

「准备这场面试」:把收到面试邀约的公司与岗位(及投递时用的简历)带入面灵面试助手——确保对应岗位存在,面试助手开场默认选中它。回包含网页端直接创建模拟 / 实时面试的链接。(需要用户授权,范围 job_applications: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": {
      "company": "<company>",
      "jobTitle": "<jobTitle>",
      "target": "<target>"
    },
    "name": "prepare_invited_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesmock 模拟面试 / live 实时面试
channelNo邀约来自 Boss 直聘传 boss,来自网申投递传 applyapply
companyYes公司名
jobTitleYes岗位名
resumeIdNo简历 ID,从 list_resumes 取得

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the operation writes into the interview assistant, ensures the corresponding job target exists, defaults to selecting it, and returns a web-side creation link. It also states the required user authorization scope job_applications:write, which is important behavioral context not present in the annotations. It does not fully clarify whether an existing target is reused or updated, or whether the operation is idempotent.

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?

The description is compact and front-loads the action '准备这场面试' before explaining the imported data, side effect, return value, and authorization requirement. The em dash and parenthetical add density but not obvious waste. It is appropriately sized for the amount of information conveyed.

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 moderate-complexity mutation tool with no output schema, the description covers the core behavior, the returned link, and the auth scope. The fully described input schema and safety annotations fill in most remaining gaps. It could be stronger by clarifying side effects when the job target already exists.

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 description coverage is 100%, so the input schema already explains all five parameters, including the target enum and channel enum. The description reinforces company, job title, resume context, and mock/live targeting but adds little beyond the schema. The baseline of 3 is appropriate.

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 states a specific action: bring the invited company, job title, and application resume into the interview assistant, ensure the job target exists, and return a web link for creating a mock or live interview. This is more specific than a tautology and separates preparing an invited interview from actually starting one. It stops short of explicitly distinguishing itself from sibling tools such as create_interview_target or start_interview.

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?

The phrase '收到面试邀约' embeds a clear use case: preparing an interview after receiving an invitation. However, the description does not explicitly state when not to use it or which sibling tool to choose instead for adjacent workflows. Usage is therefore implied rather than fully routed.

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