Skip to main content
Glama

面灵AI 面试助手

submit_job_apply_sms_code

把用户收到的短信验证码交给网申 AI,与用户在客户端主窗口顶部手填验证码相同:AI 仍在等待时验证码直接交给这次等待、本轮接着执行;等待已结束时作为一句话发给这条对话。只有一家在等时可不传 taskId;多家在等时须传 taskId(候选见 get_job_apply_client_status)。当前没有在等验证码时如实返回。回包写明交给了哪家公司 / 岗位。需要用户电脑上的「面灵求职网申助手」客户端已登录并打开(关闭窗口后转入后台运行的同样可以);客户端不在线或版本较旧时,工具如实返回原因。(需要用户授权,范围 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": {
      "code": "<code>"
    },
    "name": "submit_job_apply_sms_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes短信验证码
taskIdNo对话 ID(taskId),从 get_job_apply_client_status 取得

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by describing two distinct delivery modes — injected into the live wait and the round continues, versus appended as a message when the wait has already ended — plus the no-waiting case, the failure modes for an offline or outdated client, the response content (which company/position received it), and the required job_applications:write authorization scope.

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-loads the core action and the two delivery branches before the taskId rule, prerequisites, and return behavior, so it reads as a purposeful sequence rather than a wall of text. It is dense but nearly every clause adds operational information; only the restatement of manual entry is slightly redundant.

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, and the description compensates by stating what the response contains and what is returned in the no-waiting and client-offline cases. Preconditions, authorization scope, and the disambiguation rule are all covered, leaving nothing an agent needs in order to call it correctly.

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%, so the baseline is 3, but the description adds real meaning: taskId is conditional on multiple tasks waiting, and its valid values come from get_job_apply_client_status. The code parameter itself is only echoed from the schema.

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 concrete verb and resource: hand the SMS verification code the user received to the web-apply AI, and explicitly equates it with the user typing the code at the top of the client main window. An agent can distinguish this from generic instruction or status tools 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit branching rules: with only one task waiting taskId may be omitted; with multiple tasks waiting taskId is mandatory, and it names get_job_apply_client_status as the source of candidates. It also states the precondition (client installed, logged in, and open or running in background) and that the tool reports honestly when nothing is waiting.

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